From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Fix infrun.c fall-out from the software single-step logic change
Date: Fri, 22 Jun 2007 12:59:00 -0000 [thread overview]
Message-ID: <20070622125946.GA9750@caradoc.them.org> (raw)
In-Reply-To: <200706221255.l5MCtWBG029939@d12av02.megacenter.de.ibm.com>
On Fri, Jun 22, 2007 at 02:55:32PM +0200, Ulrich Weigand wrote:
>
> > * infrun.c (adjust_pc_after_break): Do not assume software single-step
> > is always active if SOFTWARE_SINGLE_STEP_P is true.
> > (resume): Use gdbarch_software_single_step[_p] instead of
> > SOFTWARE_SINGLE_STEP[_P].
> > (handle_inferior_event): Do not check for SOFTWARE_SINGLE_STEP_P.
> >
> > * gdbarch.sh (software_single_step): Remove target macro.
> > * gdbarch.h, gdbarch.c: Regenerate.
>
> I've committed this as well.
Thanks - it looked right to me, but I forgot to send the mail.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-22 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 19:26 Ulrich Weigand
2007-06-21 0:11 ` Ulrich Weigand
2007-06-22 12:55 ` Ulrich Weigand
2007-06-22 12:59 ` Daniel Jacobowitz [this message]
2007-06-22 13:43 ` Ulrich Weigand
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=20070622125946.GA9750@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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