Mail Archives: djgpp/1998/07/23/02:45:55
On Wed, 22 Jul 1998, Anton Helm wrote:
> Are there other standard C library functions
> calling abort() in case of an error/exception?
I already checked that before replying to you ;-). The full list of
the functions/modules is attached below.
None of the functions seem to be relevant to your case. I don't see
`putpath' called anywhere in the exception-handling code, and the
startup code can only call abort *before* `main'. As for the rest, I
don't think you use them (`alloca' should be inlined and the library
version never used). So I'm stumped. I hope the debugger backtrace
will clarify things.
> >> gdb exits to DOS prompt (NOT to NC) and the working directory changes
> >> to the one before invoking NC.
> >
> >This means that NC is aborted as well. I don't know why.
> Even more, the NC screen is restored on the DOS window but the prompt
> now belongs to dos and no longer to NC (e.g. NC screen is scrolling out
> of the window when pressing <Enter>).
So it seems like NC is aborted after it redraws the screen.
Here's the list of library modules that call `abort':
src/debug/fsdb/fullscr.c
src/libc/compat/stdlib/alloca.c
src/libc/crt0/crt1.c
- Raw text -