home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sys5.r3:191 comp.sys.m68k:1531
- Path: sparky!uunet!math.fu-berlin.de!news.th-darmstadt.de!adams
- From: adams@pdv2.fmr.maschinenbau.th-darmstadt.de (Adams)
- Newsgroups: comp.unix.sys5.r3,comp.sys.m68k
- Subject: sysV68R7.[01] --- signal handling and debugging
- Date: 10 Jan 93 23:52:34
- Organization: TH-Darmstadt
- Lines: 29
- Distribution: comp
- Message-ID: <ADAMS.93Jan10235234@PDV2.pdv2.fmr.maschinenbau.th-darmstadt.de>
- NNTP-Posting-Host: pdv2.fmr.maschinenbau.th-darmstadt.de
-
-
-
- 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
-
-
-
-
-
-