From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: frame_register_unwind(): "frame != NULL" assertion failure
Date: Thu, 13 Feb 2003 23:27:00 -0000 [thread overview]
Message-ID: <1030213232706.ZM8198@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <kevinb@redhat.com> "Re: frame_register_unwind(): "frame != NULL" assertion failure" (Feb 13, 2:48pm)
Here's one possible "fix" for the assertion failure. I've come to the
conclusion that the real culprit is get_next_frame(), but, unfortunately,
the rest of gdb is not yet ready for it to return the sentinel frame.
(See the comment in the patch for more info.) So, until it is, I propose
that we use this hack...
* frame.c (create_sentinel_frame): Make static. Add forward
declaration.
(frame_register_unwind): Add hack for converting NULL frames
into a sentinel frame.
Index: frame.c
===================================================================
RCS file: /cvs/src/src/gdb/frame.c,v
retrieving revision 1.66
diff -u -p -r1.66 frame.c
--- frame.c 2 Feb 2003 20:31:43 -0000 1.66
+++ frame.c 13 Feb 2003 23:20:22 -0000
@@ -39,6 +39,8 @@
#include "command.h"
#include "gdbcmd.h"
+static struct frame_info * create_sentinel_frame (struct regcache *regcache);
+
/* Flag to indicate whether backtraces should stop at main. */
static int backtrace_below_main;
@@ -180,6 +182,15 @@ frame_register_unwind (struct frame_info
gdb_assert (realnump != NULL);
/* gdb_assert (bufferp != NULL); */
+ /* Note: kevinb/2003-02-13: This is a hack. The problem is that
+ get_next_frame() can return NULL when it really ought to be
+ returning the sentinel frame. So, when we detect frame == NULL,
+ just use the sentinel frame instead.
+ FIXME: Remove this hack once get_next_frame() has been fixed
+ to never return NULL. */
+ if (frame == NULL)
+ frame = create_sentinel_frame (current_regcache);
+
/* NOTE: cagney/2002-11-27: A program trying to unwind a NULL frame
is broken. There is always a frame. If there, for some reason,
isn't, there is some pretty busted code as it should have
@@ -429,7 +440,7 @@ frame_map_regnum_to_name (int regnum)
/* Create a sentinel frame. */
-struct frame_info *
+static struct frame_info *
create_sentinel_frame (struct regcache *regcache)
{
struct frame_info *frame = FRAME_OBSTACK_ZALLOC (struct frame_info);
next prev parent reply other threads:[~2003-02-13 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 21:24 Kevin Buettner
2003-02-13 21:29 ` Daniel Jacobowitz
2003-02-13 21:35 ` Kevin Buettner
2003-02-13 21:48 ` Kevin Buettner
2003-02-13 23:27 ` Kevin Buettner [this message]
2003-02-14 14:58 ` Andrew Cagney
2003-02-14 15:14 ` Daniel Jacobowitz
2003-02-14 15:24 ` Kevin Buettner
2003-02-17 15:37 ` Andrew Cagney
2003-02-17 23:21 ` Kevin Buettner
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 1:59 ` Kevin Buettner
2003-02-18 22:51 ` Andrew Cagney
2003-02-20 16:18 ` Kevin Buettner
2003-02-20 16:28 ` Andrew Cagney
2003-02-20 16:36 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1030213232706.ZM8198@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox