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

On Tue, 2006-10-17 at 11:46 -0400, Daniel Jacobowitz wrote:
> On Fri, Oct 06, 2006 at 11:31:16AM -0700, Michael Snyder wrote:
> > 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...
> 
> In fact, I was working on gdbserver support for tls.exp this morning,
> and that's one of the affected tests.  So I made this change,
> tested it with x86-64 gdbserver, and committed it.
> 
> It fixes a bunch of failures in linux-dp.exp and thread-specific.exp,
> and lets more tests run for pthreads.exp.

Cool!  Then consider this patch withdrawn.



      parent reply	other threads:[~2006-10-17 20:08 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
2006-10-17 15:46       ` Daniel Jacobowitz
2006-10-17 15:53         ` Daniel Jacobowitz
2006-10-17 20:08         ` Michael Snyder [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=1161115683.14535.376.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