Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Stop infrun from tracking breakpoint insertion status.
Date: Wed, 28 Nov 2007 12:50:00 -0000	[thread overview]
Message-ID: <200711281550.19335.vladimir@codesourcery.com> (raw)
In-Reply-To: <200711271814.lARIECVU018918@d12av02.megacenter.de.ibm.com>

On Tuesday 27 November 2007 21:14:12 Ulrich Weigand wrote:
> Vladimir Prus wrote:
> 
> > There were in fact two distinct problems. The first was
> > in my previous patch to document infrun logic -- while the
> > patch was meant to have no logic change, the case of 
> > stepping over breakpoint using software single step was
> > messed up. This patch fixes the problem -- it was tested
> > on arm-linux/qemu, which uses software single step, with
> > no test result changes. OK?
> 
> Ah, right.  Sorry for missing that.
> 
> >         * infrun.c (resume): Set right thread
> >         even if stepping over breakpoint using software
> >         single step.
> 
> This is OK.

Thanks. This one is checked in.

- Volodya


  reply	other threads:[~2007-11-28 12:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 11:41 Vladimir Prus
2007-11-19 11:39 ` Ulrich Weigand
2007-11-19 17:00   ` Vladimir Prus
2007-11-20 20:48   ` Vladimir Prus
2007-11-22  0:49     ` Ulrich Weigand
2007-11-22 15:21       ` Vladimir Prus
2007-11-26 15:25         ` Ulrich Weigand
2007-11-27 17:49           ` Vladimir Prus
2007-11-27 18:14             ` Ulrich Weigand
2007-11-28 12:50               ` Vladimir Prus [this message]
2007-11-27 18:55           ` Vladimir Prus
2007-11-28 22:24             ` Ulrich Weigand
2007-11-29 18:46               ` Vladimir Prus

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=200711281550.19335.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --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