From: Andrew Cagney <ac131313@redhat.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Mark Kettenis <kettenis@chello.nl>,
GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [offbyone RFC] Merge i386newframe
Date: Fri, 14 Mar 2003 15:59:00 -0000 [thread overview]
Message-ID: <3E71FC4B.5000100@redhat.com> (raw)
In-Reply-To: <3E71C2F9.3060504@suse.cz>
>
> I suspect Daniel's answered this. The frame ID needs to be constant through out the lifetime of the frame. Getting that right isn't trivial. However, getting it right can receive a bonus: d10v now passing mips_pro.exp.
>
> You mean the whole ID should be constant or just id.base? If id.pc must be constant as well, it couldn't represent the PC register anymore...
> I'm confused.
At present, just the base needs to be constant.
However, to differentiate between two frameless functions, and to
re-find a frameless function, both the frame base and the frame
function's start address need to be compared. GDB doesn't yet do this
and when it does, it may need to refine what that PC value is.
"frame.h" mentions the problem.
Andrew
next prev parent reply other threads:[~2003-03-14 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 22:06 Michal Ludvig
2003-03-12 22:42 ` Daniel Jacobowitz
2003-03-13 19:05 ` Andrew Cagney
2003-03-13 22:46 ` Mark Kettenis
2003-03-14 15:48 ` Andrew Cagney
2003-03-14 16:19 ` Andrew Cagney
2003-03-14 18:20 ` Andrew Cagney
2003-04-06 17:10 ` Andrew Cagney
2003-04-07 18:53 ` Mark Kettenis
2003-03-14 11:54 ` Michal Ludvig
2003-03-14 15:59 ` Andrew Cagney [this message]
2003-03-14 15:43 ` Michal Ludvig
2003-03-16 12:48 ` Mark Kettenis
2003-03-17 7:52 ` Michal Ludvig
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=3E71FC4B.5000100@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mludvig@suse.cz \
/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