Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
	gdb-patches@sourceware.org, 	Pedro Alves <pedro@codesourcery.com>
Subject: Re: [new patch] Re: [RFC] Fix for gdb crash in "info thread" after 	exec().
Date: Thu, 05 Jun 2008 20:43:00 -0000	[thread overview]
Message-ID: <20080605204240.GB3818@caradoc.them.org> (raw)
In-Reply-To: <1212686557.3601.369.camel@localhost.localdomain>

On Thu, Jun 05, 2008 at 10:22:37AM -0700, Michael Snyder wrote:
> On Wed, 2008-06-04 at 18:16 -0700, Paul Pluzhnikov wrote:
> > Ping,
> > 
> > http://sourceware.org/ml/gdb-patches/2008-05/msg00727.html
> > 
> > On Wed, May 28, 2008 at 11:01 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> > ...
> > > New patch attached.  Can anyone approve (or reject) this?
> 
> Well, I'll throw my two cents in and say that it looks
> reasonable -- I'd give good odds that it's right, but it's
> been too long since I worked closely on linux threads for
> me to say positively.  

You're right - the patch is correct :-)

Pedro, could you add an FSF copyright notice to the new C file before
you check it in?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-06-05 20:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 22:12 Paul Pluzhnikov
2008-05-28  7:10 ` Paul Pluzhnikov
2008-05-28 15:27   ` Pedro Alves
2008-05-28 17:10     ` Paul Pluzhnikov
2008-05-28 21:25       ` [new patch] " Pedro Alves
2008-05-28 21:34         ` Paul Pluzhnikov
2008-05-28 22:24           ` Pedro Alves
2008-06-05  1:16             ` Paul Pluzhnikov
2008-06-05 17:23               ` Michael Snyder
2008-06-05 20:43                 ` Daniel Jacobowitz [this message]
2008-06-05 21:07                   ` Pedro Alves
2008-05-28 17:49     ` Paul Pluzhnikov

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=20080605204240.GB3818@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@specifix.com \
    --cc=pedro@codesourcery.com \
    --cc=ppluzhnikov@google.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