This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/533: Get msg 'signal handler called' on noprint/nostop signal
- From: rivers at lexmark dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 6 May 2002 17:28:05 -0000
- Subject: gdb/533: Get msg 'signal handler called' on noprint/nostop signal
- Reply-to: rivers at lexmark dot com
>Number: 533
>Category: gdb
>Synopsis: Get msg 'signal handler called' on noprint/nostop signal
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon May 06 10:38:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Martin Rivers
>Release: gdb 5.2
>Organization:
>Environment:
Sparc/Solaris SunOS 5.8
>Description:
When debugging a proces which has a SIGALRM delivered to it
every 0.01 second, and while single stepping (either via the
NEXT/STEP command) thru non-signal code, a message is emitted saying
<signal handler called>
Yet the signal number is not displayed. The pc is set at
sigacthandler. If I stepi thru this function I'll end up
in the signal handler function I've declared to handle SIGALRM.
Attempting to do a NEXT/STEP directly from the message results
in another message:
(gdb) n
(gdb)
(gdb)
(gdb)
<signal handler called>
(gdb) where 3
#0 <signal handler called>
(gdb) n
Single stepping until exit from function sigacthandler,
which has no line number information.
warning: Cannot insert breakpoint 0:
Cannot access memory at address 0x8
(gdb)
This problem does not occur in gdb 4.18 with exactly the same
program run on the same workstation.
>How-To-Repeat:
>Fix:
If I set a breakpoint at the next C statement in the non-signal
code and issue a 'CONTINUE', I can hit the breakpoint. However,
this happens so often as to interfere with productive
debugging. This does not occur in gdb version 4.18
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="None."
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="None."