From: Fred Fish <fnf@ninemoons.com>
To: Elena Zannoni <ezannoni@redhat.com>, fnf@redhat.com
Cc: gdb-patches@sources.redhat.com, fnf@redhat.com
Subject: Re: [RFA] Handle sh-elf-gcc scheduling code into a prologue when no debug info present
Date: Mon, 16 Feb 2004 18:15:00 -0000 [thread overview]
Message-ID: <200402161114.57944.fnf@ninemoons.com> (raw)
In-Reply-To: <16432.58615.340874.880645@localhost.redhat.com>
On Monday 16 February 2004 08:42, Elena Zannoni wrote:
> Is this in our testsuite? (it looks familiar) If not could it be added?
It is not in there directly, but was found as a side effect of
gdb1291. I'll go ahead and report it as a distinct gdb bug to get a
bug number and then add a test in gdb.arch.
> > With the attached patch, the prologue scanner returns the pc of the
> > jsr instruction, allowing the breakpoint at main to be hit before the
> > breakpoint at sub1:
>
> OK.
I'll post an updated patch when I have a test ready to go with it, and
then check them in.
-Fred
next prev parent reply other threads:[~2004-02-16 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 22:05 Fred Fish
2004-02-16 15:47 ` Elena Zannoni
2004-02-16 18:15 ` Fred Fish [this message]
2004-02-19 23:10 ` Fred Fish
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=200402161114.57944.fnf@ninemoons.com \
--to=fnf@ninemoons.com \
--cc=ezannoni@redhat.com \
--cc=fnf@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