From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/sparc] Fix step-bt.exp: backtrace after second instruction step
Date: Thu, 09 Nov 2006 16:37:00 -0000 [thread overview]
Message-ID: <20061109163732.GB3505@adacore.com> (raw)
In-Reply-To: <20061109130010.GA1625@nevyn.them.org>
> > I encountered on sparc the same problem I saw on i386: When scanning
> > a function prologue, if an instruction is replaced by a breakpoint,
> > we read the breakpoint instead of reading the original instruction.
> >
> > Fixed using the same method as in i386...
>
> OK.
Thank you. Checked in.
--
Joel
prev parent reply other threads:[~2006-11-09 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 4:57 Joel Brobecker
2006-11-09 13:00 ` Daniel Jacobowitz
2006-11-09 16:37 ` Joel Brobecker [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=20061109163732.GB3505@adacore.com \
--to=brobecker@adacore.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