1. Windows console error exit
Is there any way to get a exw console program not to hang with a "Press
Enter..." after an abnormal exit? Even if you set crash_file("") it still hangs.
I'm using one program to open another, but if the second one fails for some
reason, it is stuck there forever. Ideally, I would like the ex.err file to be
created, but for the program to exit without any interaction from the user.
???
2. Re: Windows console error exit
On Thu, 29 Apr 2004 09:40:44 -0700, Andy Serpa
<guest at RapidEuphoria.com> wrote:
>after an abnormal exit?
Define abnormal exit.
It is trivial to catch abort(n) but It sounds you are looking for a
shortcut me & many would scream over.
Regards,
Pete
3. Re: Windows console error exit
A syntax error, type error, 1/0 error -- anything that causes an ex.err file to
be created. I have a parent program running a child program. I want the parent
to be able to re-run the child if the child crashes -- the child crashing in this
context can be considered normal behavior -- the parent will examine the
resulting ex.err file. But the child never exits because it is sitting there
with a "Press Enter...". I can TerminateProcess() the child, but then I have to
come up with some complex way to determine if the child has aborted (but is
hanging). It would be much better if the process simply terminated itself. I
imagine if I bought the source code, this would be a trivial change, or maybe
someone can compile me such a version?
