how@IVY.UCDAVIS.EDU (W. Wilson Ho) (07/18/89)
------- Start of forwarded message ------- From: crawford@ivy (Rick Crawford) To: debug@ivy Cc: crawford@ivy Subject: gdb signal bug Date: Sun, 16 Jul 89 18:11:17 PDT Here's a newly discovered bug (or UN-implemented feature) in standard gdb versions 2.7 thru 3.1: If we stop at a breakpoint and manually tell gdb to CONT the inferior, giving it a signal, we remain stuck at that breakpoint. GDB 3.1, Copyright (C) 1988 Free Software Foundation, Inc. (gdb) b main Breakpoint 1 at 0x54: file send.c, line 21. (gdb) r Starting program: /usr/pkg/debug/rick/dalek/t/send Bpt 1, main (argc=1, argv=(char **) 0x7fffe06c, 2147475572) (send.c line 29) (gdb) sig 3 Continuing with signal 3. Bpt 1, main (argc=1, argv=(char **) 0x7fffe06c, 2147475572) (send.c line 29) (gdb) sig 3 Continuing with signal 3. Bpt 1, main (argc=1, argv=(char **) 0x7fffe06c, 2147475572) (send.c line 29) (gdb) (gdb) info program Program being debugged is in process 18734, stopped at 0x54. It stopped at breakpoint 1. Type "info stack" or "info reg" for more information. (gdb) I tried the following combinations, but PASS is the only relevant one: (gdb) i sig 3 Number Stop Print Pass to program Description 3 Yes Yes Yes Quit {default} 3 No Yes Yes Quit 3 No No Yes Quit 3 No No No Quit ------- End of forwarded message -------