Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: nickrob@snap.net.nz, denis.pilat@st.com, gdb@sourceware.org
Subject: Re: info thread
Date: Sat, 23 Sep 2006 21:59:00 -0000	[thread overview]
Message-ID: <20060923215947.GA29366@nevyn.them.org> (raw)
In-Reply-To: <200609231905.k8NJ5ucX001839@elgar.sibelius.xs4all.nl>

On Sat, Sep 23, 2006 at 09:05:56PM +0200, Mark Kettenis wrote:
> Note that the formatting of the thread ID produced by to_pid_to_str is
> highly dependent on the specific threads model in use.  The thread
> extra info is also mostly free-form.  That means it might not be wise
> to export that information in the MI interface.

Except as strings, presumably?

It's supposed to be useful to users; the extra information is supposed
to be exactly what would be useful in a dialog box listing threads.

I agree that some words in the MI documentation about which strings
to consider "opaque" may be in order, here and in other places (e.g.
relating to frames...)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-09-23 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 21:49 Nick Roberts
2006-09-19 13:16 ` Denis PILAT
2006-09-19 14:23   ` Daniel Jacobowitz
2006-09-19 20:55   ` Nick Roberts
2006-09-19 21:03     ` Daniel Jacobowitz
2006-09-23 19:06       ` Mark Kettenis
2006-09-23 21:59         ` Daniel Jacobowitz [this message]
2006-09-25 14:49           ` Denis PILAT
2006-09-25 14:52             ` Daniel Jacobowitz
2006-09-25 18:39           ` Michael Snyder
2006-09-25 15:25 Alain Magloire
2006-09-25 15:31 ` Daniel Jacobowitz
2006-09-25 16:25 Alain Magloire
2006-09-25 17:27 Alain Magloire
2006-09-25 17:36 ` Daniel Jacobowitz
2006-09-27 14:18 ` Denis PILAT
2006-09-28 14:35 Alain Magloire

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=20060923215947.GA29366@nevyn.them.org \
    --to=drow@false.org \
    --cc=denis.pilat@st.com \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=nickrob@snap.net.nz \
    /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