This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1769: segmentation fault for killing debugged program with ctrl-c
- From: dima at cc dot hut dot fi
- To: gdb-gnats at sources dot redhat dot com
- Date: 1 Sep 2004 12:14:24 -0000
- Subject: gdb/1769: segmentation fault for killing debugged program with ctrl-c
- Reply-to: dima at cc dot hut dot fi
>Number: 1769
>Category: gdb
>Synopsis: segmentation fault for killing debugged program with ctrl-c
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Sep 01 12:18:02 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: dima@cc.hut.fi
>Release: 6.0
>Organization:
>Environment:
>Description:
when I ctrl-c a program ran under gdb, gdb exits with segmentation fault. Here's how it looks when gbd is ran under gdb too:
Program received signal SIGINT, Interrupt.
Program received signal SIGSEGV, Segmentation fault.
0x0815f3e7 in dwarf2_frame_base_p ()
(gdb) bt
#0 0x0815f3e7 in dwarf2_frame_base_p ()
#1 0x0815ee8f in dwarf2_frame_sniffer ()
#2 0x08118219 in frame_unwind_find_by_frame ()
#3 0x0811796c in get_frame_type ()
#4 0x080c39cd in print_frame_info ()
#5 0x080c34e8 in unset_in_environ ()
#6 0x0810e901 in catch_exceptions ()
#7 0x0810e830 in throw_exception ()
#8 0xbfffefc0 in ?? ()
#9 0xbfffeeb8 in ?? ()
#10 0x080c0041 in normal_stop ()
Previous frame inner to this frame (corrupt stack?)
(gdb)
>How-To-Repeat:
shell: gdb gdb
gdb1: run sometestprogram
gdb2: run
^C
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: