sysV68R7.[01] --- signal handling and debugging

Thread View: comp.unix.sys5.r3

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Adams Sun, 10 Jan 1993 23:52

#87

Author: Adams
Date: Sun, 10 Jan 1993 23:52

24 lines
1304 bytes


We had GDB-3.5 up and running for 2 years under R[456]..x, 
converting to R7.x exhibited following behaviour:

Unchanged GDB-3.5, compiled under R6.2 and working, stopped itself
debugging a program telling "Aborted by SIGILL at 0xffffffff
[SIG_DEFAULT]", if target hits a break point.

ptrace interface of GDB changed to SIGTRAP as proposed in the NEW man
pages of R7.0, yields same behaviour as above, SIGILL just changed to
SIGTRAP.

Might there be a problem, that signals sent to the target, are
also delivered to the debugger?  

Up to now my impression was, that the kernel just has to return the 
debugger from its "wait" call and pass the waitstatus including signal
number of ptraced child as a return value to the debugger.

Were there massive changes regarding kernel interface between 
R6.2 and R7.[01] ?

best adams

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads