Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: lace@jankratochvil.net, gdb-patches@sourceware.org,
	        bartoschek@or.uni-bonn.de
Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Thu, 13 Jul 2006 18:50:00 -0000	[thread overview]
Message-ID: <200607131849.k6DInqeJ029991@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060713040135.GY24622@nevyn.them.org> (message from Daniel 	Jacobowitz on Thu, 13 Jul 2006 00:01:35 -0400)

> Date: Thu, 13 Jul 2006 00:01:35 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> 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.

Probably a good idea, given the fact that it's unlikely we'll see a
N:M threads library on Linux is the near future.

> 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.

Doesn't your simplification of thread_db_pid_to_str() lose some useful
information about the extra system thread that the LinuxThreads
library used to have (I'm not sure if that wart is still present in
NPTL)?

You might want to look at implementing to_extra_thread_info() to give
some state information; see bsd-uthread.c for an example.

Mark

> 2006-07-12  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* linux-thread-db.c (td_thr_getfpregs_p, td_thr_getgregs_p)
> 	(td_thr_setfpregs_p, td_thr_setgregs_p, thread_db_get_info)
> 	(thread_db_fetch_registers, thread_db_store_registers)
> 	(thread_db_thread_alive): Delete.
> 	(thread_db_load): Don't look up regset functions.
> 	(thread_db_pid_to_str): Simplify.
> 	(init_thread_db_ops): Do not set to_fetch_registers,
> 	to_store_registers, or to_thread_alive.


  parent reply	other threads:[~2006-07-13 18:50 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 [this message]
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
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=200607131849.k6DInqeJ029991@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=bartoschek@or.uni-bonn.de \
    --cc=drow@false.org \
    --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