Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Cleanup MI testsuite
Date: Wed, 26 Mar 2008 15:41:00 -0000	[thread overview]
Message-ID: <fsdqpm$28h$1@ger.gmane.org> (raw)
In-Reply-To: <200803261511.57740.pedro@codesourcery.com>

Pedro Alves wrote:

> A Wednesday 26 March 2008 13:29:52, Vladimir Prus wrote:
>> When I've checked in the patch to implement per-thread varobjs, I've
>> implicitly assumed that MI output does not change in single-threaded
>> programs, so no testsuite update is necessary. However, that's not
>> necessary true, and with Pedro's recent patch, is not true on x86.
> 
> My patch affected every linux native target, independently
> of arch.  Were you testing on Cygwin instead for example, when you
> get to main, there's already 2 threads listed in info threads.  The
> main thread and another one internal to cygwin1.dll.

Yes, that why I said "not necessary true" -- your patch just exposed
the problem that was already there.

- Volodya




      reply	other threads:[~2008-03-26 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 13:30 Vladimir Prus
2008-03-26 15:12 ` Pedro Alves
2008-03-26 15:41   ` Vladimir Prus [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='fsdqpm$28h$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --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