From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Fix some frame problems in the mn10300 prologue analyzer
Date: Wed, 30 Jul 2003 20:45:00 -0000 [thread overview]
Message-ID: <1030730204519.ZM13135@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <kevinb@redhat.com> "[RFC] Fix some frame problems in the mn10300 prologue analyzer" (Jul 22, 11:58am)
On Jul 22, 11:58am, Kevin Buettner wrote:
> * mn10300-tdep.c (analyze_dummy_frame): Pass ``pc'' so that
> the prologue analyzer won't need to attempt to extract the pc
> value from the woefully incomplete dummy frame.
> (mn10300_analyze_prologue): Avoid calls to get_frame_pc() when
> possible. Disable code which modifies the frame.
Committed.
prev parent reply other threads:[~2003-07-30 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 18:58 Kevin Buettner
2003-07-30 20:45 ` Kevin Buettner [this message]
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=1030730204519.ZM13135@localhost.localdomain \
--to=kevinb@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