Mail Archives: djgpp/1997/04/01/05:12:49
On Thu, 27 Mar 1997, Eli Zaretskii wrote:
> As far as I can see, `abort' doesn't generate any signal at all, it
> just exits after printing "Abort!". So unless RHIDE changes anything
> in its integrated debugger, SIGABRT has nothing to do with `abort'.
Oh yes. I had in my head the changes which I mad to RHIDE. I wrote
my own abort() to get a gracefull abort and there I call also
'raise(SIGABRT)'.
> In fact, I think SIGABRT is not generated and not handled anywhere in
The modified version of 'go32target.c' which I'm using (the patch
is included in the RHIDE sources) handles now the signals from
the debuggee, or better, it reports the signals ow correct
to gdb and kills the program for any signal except SIGTRAP.
Robert
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post: Am Berg 3, D-09573 Dittmannsdorf *
* e-Mail: Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE *
* WWW: http://www.tu-chemnitz.de/~rho *
*****************************************************************
- Raw text -