This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/13866] New: crashes from stale frame_info *
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 18 Mar 2012 18:20:01 +0000
- Subject: [Bug backtrace/13866] New: crashes from stale frame_info *
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13866
Bug #: 13866
Summary: crashes from stale frame_info *
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: backtrace
AssignedTo: unassigned@sourceware.org
ReportedBy: jan.kratochvil@redhat.com
Classification: Unclassified
Target: x86_64-unknown-linux-gnu
https://bugzilla.redhat.com/show_bug.cgi?id=804256
Even FSF GDB HEAD has still stale frame_info pointers:
#1 in freehook (ptr=0xb3c45e0, caller=0x825759) at mcheck.c:211
#2 in xfree (ptr=0xb3c45e0) at ./common/common-utils.c:107
#3 in obstack_free (h=0x1d4ac20, obj=0x0) at obstack.c:367
#4 in reinit_frame_cache () at frame.c:1542
#5 in switch_to_thread (ptid=...) at thread.c:989
#6 in switch_to_program_space_and_thread (pspace=0x27c38a0) at progspace.c:494
#7 in skip_prologue_sal (sal=0x24ec190) at symtab.c:2694
#8 in decode_all_digits () at linespec.c:2523
#9 in decode_line_internal () at linespec.c:1132
#10 in decode_line_1 (flags=1default_line=81) at linespec.c:1344
#11 in until_break_command (arg="",from_tty=1,anywhere=0) at breakpoint.c:10532
There are currently too many situations with stale frame_info * after
switch_to_* invalidate them now, IMO reinit_frame_cache needs to be removed in
these simple cases.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.