From: Michal Ludvig <mludvig@suse.cz>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add a sentinel frame
Date: Mon, 10 Feb 2003 23:36:00 -0000 [thread overview]
Message-ID: <3E48378E.6090007@suse.cz> (raw)
In-Reply-To: <3E305670.3020700@redhat.com>
Andrew Cagney wrote:
> Hello,
>
> This patch modifies^D^D^D^Dsimplifies the frame code so that there is an
> extra frame below the innermost frame. That extra frame maps any
> request for a register onto the regcache.
>
> The thing to notice with this patch is how it eliminates the need to
> special case a level zero frame when fetching a frame's register.
> Instead, a register can be fetched using the recursive frame_register()
> method.
>
> I'll look to commit this in a few days.
>
> Follow on patches include:
> - convert d10v to the current frame unwind mechanims
> - deprecate methods such as POP_FRAME.
>
> Andrew
Hi Andrew,
I'm getting lots of internal errors due to the fact that this function
is called while running x86-64 testsuite on mainline.
> +static void
> +sentinel_frame_pop (struct frame_info *frame,
> + void **cache,
> + struct regcache *regcache)
> +{
> + internal_error (__FILE__, __LINE__, "Function sentinal_frame_pop called");
> +}
How can I avoid these errors?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
next prev parent reply other threads:[~2003-02-10 23:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 20:54 Andrew Cagney
2003-01-27 21:42 ` Andrew Cagney
2003-02-10 23:36 ` Michal Ludvig [this message]
2003-02-11 16:48 ` Andrew Cagney
2003-02-18 11:21 ` Michal Ludvig
2003-02-19 13:27 ` Andrew Cagney
2003-02-19 14:04 ` Daniel Jacobowitz
2003-02-19 16:46 ` Andrew Cagney
2003-02-19 16:56 ` Daniel Jacobowitz
2003-02-19 17:11 ` Andrew Cagney
2003-02-19 17:17 ` Daniel Jacobowitz
2003-02-19 17:46 ` Andrew Cagney
2003-02-19 17:56 ` Daniel Jacobowitz
2003-02-19 18:36 ` Andrew Cagney
2003-02-19 18:52 ` Daniel Jacobowitz
2003-02-19 20:22 ` Andrew Cagney
2003-02-19 20:39 ` Daniel Jacobowitz
2003-02-19 21:21 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-19 21:45 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-25 16:24 ` Michal Ludvig
2003-02-25 19:43 ` Andrew Cagney
2003-02-25 21:00 ` Michal Ludvig
2003-02-25 21:12 ` Andrew Cagney
2003-02-26 8:04 ` Michal Ludvig
2003-02-27 18:27 ` Andrew Cagney
2003-02-28 13:02 ` Michal Ludvig
2003-02-28 15:48 ` Andrew Cagney
2003-03-05 17:38 ` Michal Ludvig
2003-03-05 18:25 ` Andrew Cagney
2003-03-06 16:00 ` Michal Ludvig
2003-03-06 20:13 ` Andrew Cagney
2003-03-06 22:42 ` [RFA] Dummy frames on x86-64 Michal Ludvig
2003-03-07 14:50 ` Andrew Cagney
2003-02-25 22:41 ` [patch/rfc] Add a sentinel frame Andrew Cagney
2003-02-25 21:21 Michael Elizabeth Chastain
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=3E48378E.6090007@suse.cz \
--to=mludvig@suse.cz \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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