Archived issue #0027043
Draw is sometimes crashed unexpectedly during running of test command
Description
When I run the tests in manual mode (test command) sometimes Draw is crashed.
E.g., the script in steps to reproduce gets draw to crash on 9th iteration on my PC.
E.g., the script in steps to reproduce gets draw to crash on 9th iteration on my PC.
Steps to reproduce
repeat 10 {test boolean gdml_private E4}
Public activity
5 archived notes
Participants are labeled by their role within this record.
When running under debugger, the following debug assertion is raised:
Program: D:\git\occt1\build\win64\vc12\bind\DRAWEXE.exe
File: f:\dd\vctools\crt\crtw32\lowio\dup2.c
Line: 59
Expression: (fh1 >= 0 && (unsigned)fh1 < (unsigned)_nhandle)
The stack trace is shown:
msvcr120d.dll![revision removed]() Unknown
> TKDraw.dll!`anonymous namespace'::capture_end(OSD_File * tmp_file, int std_fd, int save_fd, std::basic_ostream<char,std::char_traits<char> > & log, unsigned int doEcho) Line 90 C++
TKDraw.dll!CommandCmd(void * theClientData, Tcl_Interp * interp, int argc, const char * * argv) Line 203 C++
The line in our code is (Draw_Interpretor.cxx):
89: dup2(save_fd, std_fd);
It seems assertion is raised during duplication of the standard error channel.
Program: D:\git\occt1\build\win64\vc12\bind\DRAWEXE.exe
File: f:\dd\vctools\crt\crtw32\lowio\dup2.c
Line: 59
Expression: (fh1 >= 0 && (unsigned)fh1 < (unsigned)_nhandle)
The stack trace is shown:
msvcr120d.dll![revision removed]() Unknown
> TKDraw.dll!`anonymous namespace'::capture_end(OSD_File * tmp_file, int std_fd, int save_fd, std::basic_ostream<char,std::char_traits<char> > & log, unsigned int doEcho) Line 90 C++
TKDraw.dll!CommandCmd(void * theClientData, Tcl_Interp * interp, int argc, const char * * argv) Line 203 C++
The line in our code is (Draw_Interpretor.cxx):
89: dup2(save_fd, std_fd);
It seems assertion is raised during duplication of the standard error channel.
Error disappears if we turn off logging, either by running "dlog off" command, or by adding "1" option to the end of "test" command.
On my home computer similar problem is reproduces as follows:
1. Copy text "test perf bapline intersect" to buffer
2. Start DRAW
3. Paste the text
4. Press Enter
==> The test starts but crashes with message "error writing "stdout": bad file number"
Notably if the same text is input directy instead of copy / paste, it works OK
1. Copy text "test perf bapline intersect" to buffer
2. Start DRAW
3. Paste the text
4. Press Enter
==> The test starts but crashes with message "error writing "stdout": bad file number"
Notably if the same text is input directy instead of copy / paste, it works OK
This is not for my work PC. This test always work OK.
This bug has been fixed with #0027620.
Please close it.
Please close it.
Related records