Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>, manjo@austin.ibm.com
Cc: msnyder@redhat.com, gilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] New thread testcase.
Date: Tue, 10 Aug 2004 15:13:00 -0000	[thread overview]
Message-ID: <4118E61B.3060902@gnu.org> (raw)
In-Reply-To: <41187827.nailB8H1E9AWV@mindspring.com>

> Hi Manoj,
> 
> I am not the maintainer of gdb.threads -- that is Michael Snyder.
> (See the gdb/MAINTAINERS file for a list of who maintains what
> subdirectory).  You'll have to work with Michael Snyder on this
> patch.  I can give you some feedback though.
> 
> The basic idea of the test is good but it needs revision.  Don't get
> discouraged by the long list that follows.  I spent some time
> proof-reading this because I think it's good and I want it to get in.
> 
> Also, since this is Michael Snyder's area, anything he says
> outweighs anything I say.  The changes below are just my advice.

Manoj,

You've got me curious.  Do any of the existing tests exercise this bug 
(manythreads.exp comes to mind)?   Oh, and what is the bug? :-)

Andrew



  reply	other threads:[~2004-08-10 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 22:18 [patch/testsuite/mi/copyright] gdb.mi/mi2-*.exp: update copyright years Michael Chastain
2004-08-10  6:10 ` [RFC] New thread testcase Manoj Iyer
2004-08-10  7:24   ` Michael Chastain
2004-08-10 15:13     ` Andrew Cagney [this message]
2004-08-10 20:22       ` Manoj Iyer
2004-08-10 20:33         ` Andrew Cagney
2004-08-10 20:44           ` Manoj Iyer
2004-08-12 16:04             ` Andrew Cagney
2004-08-27  3:25             ` Michael Snyder
2004-08-27 13:48               ` Manoj Iyer
2004-08-10 20:13     ` Manoj Iyer
2004-08-12  0:26   ` Michael Snyder

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=4118E61B.3060902@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gilliam@us.ibm.com \
    --cc=manjo@austin.ibm.com \
    --cc=mec.gnu@mindspring.com \
    --cc=msnyder@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