Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christoph Bartoschek <bartoschek@or.uni-bonn.de>
To: Jan Kratochvil <lace@jankratochvil.net>, 	gdb-patches@sourceware.org
Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Fri, 14 Jul 2006 13:15:00 -0000	[thread overview]
Message-ID: <200607141515.53435.bartoschek@or.uni-bonn.de> (raw)
In-Reply-To: <20060713040135.GY24622@nevyn.them.org>

Am Donnerstag, 13. Juli 2006 06:01 schrieb Daniel Jacobowitz:
> On Tue, Jun 20, 2006 at 03:07:40PM -0400, Daniel Jacobowitz wrote:
> > I think the real fix to this problem is going to involve less
> > dependence on thread IDs.  I've been migrating the code away from that
> > and I'll try to find some time in the next week to finish the job;
> > maybe that will help.
>
> Here's an alternative patch that seems to work for the same test.
> Could one of you let me know if it also helps for the problems you saw?
>
> The main change is to remove the thread_db_thread_alive function.  My
> ptid_t representation change means that we can call the linux-nat.c
> implementation directly.  This change means we might have two threads
> "live" at the same time with the same TID - but they'll have different
> LWP IDs, so different PTIDs, so GDB won't get confused.
>
> It also (long overdue) removes the dependence on fill_gregset, and
> removes a not especially useful call into libthread_db for converting
> threads to strings.  There are a number of more possible cleanups,
> but this hits the big ones.


Hi,

on which revision should I apply the patch to get the most meaningful results?

Greetings 
Christoph Bartoschek


  parent reply	other threads:[~2006-07-14 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200606191719.00530.bartoschek@or.uni-bonn.de>
     [not found] ` <200606201542.12070.bartoschek@or.uni-bonn.de>
     [not found]   ` <20060620135351.GA9853@host0.dyn.jankratochvil.net>
     [not found]     ` <200606201821.41941.bartoschek@or.uni-bonn.de>
     [not found]       ` <200606201456.57681.bartoschek@or.uni-bonn.de>
     [not found]         ` <20060620130932.GA21490@nevyn.them.org>
     [not found]           ` <200606201524.45099.bartoschek@or.uni-bonn.de>
     [not found]             ` <20060620132737.GA21951@nevyn.them.org>
2006-06-19 16:56               ` Jan Kratochvil
2006-06-20 17:05                 ` RFC: " Jan Kratochvil
2006-06-20 17:11                   ` Daniel Jacobowitz
2006-06-20 18:54                     ` Jan Kratochvil
2006-06-20 19:07                       ` Daniel Jacobowitz
2006-07-13  4:01                         ` Daniel Jacobowitz
2006-07-13 13:28                           ` Jan Kratochvil
2006-07-13 13:43                             ` Daniel Jacobowitz
2006-07-13 15:07                               ` Jan Kratochvil
2006-07-13 18:50                           ` Mark Kettenis
2006-07-13 19:47                             ` Daniel Jacobowitz
2006-07-13 23:16                               ` Mark Kettenis
2006-07-18 22:55                                 ` Daniel Jacobowitz
2006-07-14 13:15                           ` Christoph Bartoschek [this message]
2006-07-14 13:36                             ` Daniel Jacobowitz

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=200607141515.53435.bartoschek@or.uni-bonn.de \
    --to=bartoschek@or.uni-bonn.de \
    --cc=gdb-patches@sourceware.org \
    --cc=lace@jankratochvil.net \
    /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