Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/gdbserver] Update current inferior when using vCont
Date: Sun, 29 Feb 2004 16:49:00 -0000	[thread overview]
Message-ID: <20040229164958.GE15749@nevyn.them.org> (raw)
In-Reply-To: <20040228182439.GA17159@nevyn.them.org>

On Sat, Feb 28, 2004 at 01:24:39PM -0500, Daniel Jacobowitz wrote:
> Extensive testing on a software-single-step target using vCont turned up a
> problem that testing on x86 didn't - not surprising, since gdbserver is
> stressed much harder in this case.  By not calling set_desired_inferior after
> setting cont_thread, we could end up sending signals to the wrong thread on
> an interrupt from the client.
> 
> Will commit in a bit.

> 2004-02-28  Daniel Jacobowitz  <drow@mvista.com>
> 
> 	* server.c (handle_v_cont): Call set_desired_inferior.

I've committed this to HEAD.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-02-29 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 18:24 Daniel Jacobowitz
2004-02-29 16:49 ` Daniel Jacobowitz [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=20040229164958.GE15749@nevyn.them.org \
    --to=drow@false.org \
    --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