Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: GDB Patches ML <gdb-patches@sourceware.org>,
		Daniel Jacobowitz <drow@false.org>
Subject: Re: PING Re: [RFC] thread tests, linux/gdbserver
Date: Fri, 06 Oct 2006 18:31:00 -0000	[thread overview]
Message-ID: <1160159477.9761.124.camel@localhost.localdomain> (raw)
In-Reply-To: <20713.192.87.1.22.1160132019.squirrel@webmail.xs4all.nl>

On Fri, 2006-10-06 at 12:53 +0200, Mark Kettenis wrote:
> >  Any objections to this patch?
> 
> Hmm, I must have missed the origional mail, but I think we should actually
> fix our code to print these things in a more consistent manner.

It comes from target_pid_to_str, which is a target method.
We don't officially control what it looks like, since a target
is free to say anything it likes.

Of course, we do control the remote target, which is all I'm
immediately concerned with here.  It would be a one-line 
change, I think, to capitalize it...



> 
> >  On Mon, 2006-09-25 at 15:26 -0700, Michael Snyder wrote:
> > > Several thread tests contain patterns that explicitly look
> > > for the string "Thread" (capitalized) in the info threads
> > > output.
> > >
> > > But target remote prints it as "thread" (lower case), and
> > > so even though these tests can be run against gdbserver,
> > > they will fail.
> > >
> > > This patch just substitutes a pattern "\[Tt\]hread".
> > >
> > > Seem OK?
> > >
> > >
> >
> 
> 


  reply	other threads:[~2006-10-06 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 22:26 Michael Snyder
2006-10-05 21:51 ` PING " Michael Snyder
2006-10-06 10:53   ` Mark Kettenis
2006-10-06 18:31     ` Michael Snyder [this message]
2006-10-17 15:46       ` Daniel Jacobowitz
2006-10-17 15:53         ` Daniel Jacobowitz
2006-10-17 20:08         ` 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=1160159477.9761.124.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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