Debug assertion failed with dos command on exit X2

[JRz]

Hi Nikos,

I've encountered the following bug in X2 0.0.0.37 (running on Windows XP, SP1)

When I start a Command window with a command that is monitoring a file for changes (I use tail with -f as option to follow a log file as it grows) the output is captured nicely in the special output window. When I close the output window nothing happens, but when I subsequenly stop X2, it throws a debug assertion at me. This also happens when I shut down X2 with the command window still open.
I know that a process like the tail command is somewhat awkward, since it normally doesn't finish until you hit ctrl-C. This is not possible using the output window. So this may be the cause of the problem??


error dialog and dbmon output are in the mail
Jan

[nikos]

(here's a copy of my email response for other users)

indeed the console window is not for blocking commands
if you were to do that you wouldn't be able to launch any more commands while the program was running!

x2 already knows something's wrong:

400: PIPE b8c6c0: Sending command: exit
MINI-ASSERT: pipe b8c6c0 is probably blocked & will leak

i'd recommend starting a plain dos box for such commands
you can easily do that by typing "$" in the address bar with no arguments