From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New threads test
Date: Thu, 09 Oct 2003 19:41:00 -0000 [thread overview]
Message-ID: <3F85B9DC.4020804@redhat.com> (raw)
In-Reply-To: <20031009141057.GB29621@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Wed, Oct 01, 2003 at 02:52:30PM -0400, Daniel Jacobowitz wrote:
>
>>On Wed, Oct 01, 2003 at 11:37:11AM -0700, Michael Snyder wrote:
>>
>>>Daniel Jacobowitz wrote:
>>>
>>>>This is a test for the remote protocol issue I'm solving with vCont. It
>>>>also shows up in schedlock, but the simpler test makes it much clearer
>>>>what's going wrong. OK?
>>>>
>>>
>>>Umm... what is going wrong? What are you testing for here?
>>
>>+# It tests that the correct thread is single-stepped.
>>
>>More intelligibly: when gdbserver is told to single-step one thread
>>(without holding all others schedlocked), it assumes we mean the first
>>thread. Which might not be the _right_ thread.
Hmmm... it should assume we mean the _current_ thread
(ie. the one that had a stop event). The remote protocol
should cover this (and did, last I checked).
> Hi Michael,
>
> Is this test OK (with a better comment and the copyright notice that
> Michael C suggested)?
OK, with emphasis on "more comments".
next prev parent reply other threads:[~2003-10-09 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 19:22 Daniel Jacobowitz
2003-10-01 18:37 ` Michael Snyder
2003-10-01 18:52 ` Daniel Jacobowitz
2003-10-09 14:10 ` Daniel Jacobowitz
2003-10-09 19:41 ` Michael Snyder [this message]
2003-10-09 19:49 ` Daniel Jacobowitz
2003-10-10 0:05 ` Michael Snyder
2003-10-10 1:28 ` Daniel Jacobowitz
2003-09-30 19:39 Michael Elizabeth Chastain
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=3F85B9DC.4020804@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.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