From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Thu, 13 Jul 2006 23:16:00 -0000 [thread overview]
Message-ID: <200607132316.k6DNGE9c016595@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060713194731.GA1709@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 13 Jul 2006 15:47:31 -0400)
> Date: Thu, 13 Jul 2006 15:47:31 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> > You might want to look at implementing to_extra_thread_info() to give
> > some state information; see bsd-uthread.c for an example.
>
> ... and in any case that's a better place for the state information.
> Nice. Unfortunately we don't really have useful state bits. I could
> probably move the exiting/missing text there.
That's what I had in mind...
> I'll keep that in mind for a future update, thanks!
Well, if this patch doesn't cause any regressions, there is no real
reason to hold it back. You can always add the to_extra_thread_info()
implementation later.
Mark
next prev parent reply other threads:[~2006-07-13 23:16 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 [this message]
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=200607132316.k6DNGE9c016595@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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