public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* Re: backtrace/2353: Crash requesting high "info frame" value: ../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed.
@ 2008-09-24 10:38 Richard Stuckey
0 siblings, 0 replies; 2+ messages in thread
From: Richard Stuckey @ 2008-09-24 10:38 UTC (permalink / raw)
To: nobody; +Cc: gdb-prs
The following reply was made to PR backtrace/2353; it has been noted by GNATS.
From: Richard Stuckey <richard.stuckey@arc.com>
To: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com,
ajvincent@gmail.com, gdb-prs@sources.redhat.com
Cc:
Subject: Re: backtrace/2353: Crash requesting high "info frame" value:
../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion
`fde != NULL' failed.
Date: Wed, 24 Sep 2008 11:36:43 +0100
http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2353
I have come across this problem myself, in the 6.6 and 6.8 releases.
A possible fix is to add the code:
CORE_ADDR pc;
...
pc = get_frame_pc (fi);
if (pc == 0)
{
warning("invalid frame");
return;
}
to the function frame_info in file stack.c after the call to parse_frame_specification_1
(and 'pc' can then be used in the call to find_pc_symtab a few lines later).
This fixes the problem in the ARC gdb port; however, it assumes that 0 is an invalid value for PC,
which is not necessarily true for all ports, so it may not be the "general case" fix.
Regards,
Richard Stuckey
^ permalink raw reply [flat|nested] 2+ messages in thread
* backtrace/2353: Crash requesting high "info frame" value: ../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed.
@ 2007-11-01 6:48 ajvincent
0 siblings, 0 replies; 2+ messages in thread
From: ajvincent @ 2007-11-01 6:48 UTC (permalink / raw)
To: gdb-gnats
>Number: 2353
>Category: backtrace
>Synopsis: Crash requesting high "info frame" value: ../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed.
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Nov 01 06:48:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator: ajvincent@gmail.com
>Release: GNU gdb Red Hat Linux (6.6-16.fc7rh)
>Organization:
>Environment:
Fedora 7 Linux, terminal
>Description:
Stack frame at 0xf:
eip = 0x0; saved eip
../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted
>How-To-Repeat:
(1) Fire up GDB and attach it to a process with x number of frames.
(2) info frame (x + 1)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-09-24 10:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-09-24 10:38 backtrace/2353: Crash requesting high "info frame" value: ../../gdb/dwarf2-frame.c:816: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed Richard Stuckey
-- strict thread matches above, loose matches on Subject: below --
2007-11-01 6:48 ajvincent
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).