public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: Re: Remote thread infos
Date: Tue, 16 Nov 2004 10:55:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20041116085522.01d1a9e0@NT_SERVER> (raw)
In-Reply-To: <41996289.9020907@gnu.org>


>>The remote protocol can ask for thread info and more info (qThreadExtraInfo).
>>I couldn't find an explicit description about these fields in the manual.
>>However in the source code these fields are evaluated as follows:
>>sprintf(&display_buf[n], " State: %s,", threadinfo.display);
>>sprintf(&display_buf[n], " Priority: %s", threadinfo.more_display);
>>It's quite impossible to use these fields for other info as they are explicitely
>>prepended with "State" and "Priority". But the manual says: "... may
>>contain anything that the target OS thinks is interesting for gdb to tell
>>the user about the thread."
>
>Hmm, yes.  I think they have something to do with eCos?

Don't know, I have never worked with eCos.

>>Is there a possibility to use these texts
>>from the CLI as well as MI without the prepended strings? If not
>>shouldn't the manual say what these texts are for?
>
>Would KOD be useful?  Or a more descriptive packet?

Sorry, what means KOD?

>>I know that I can take the strings and remove the leading word, I
>>just thought I mention this inconsistency with the manual.
>>Thanks

bye  Fabi


      reply	other threads:[~2004-11-16  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20  9:48 Fabian Cenedese
2004-11-16  2:21 ` Andrew Cagney
2004-11-16 10:55   ` Fabian Cenedese [this message]

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=5.2.0.9.1.20041116085522.01d1a9e0@NT_SERVER \
    --to=cenedese@indel.ch \
    --cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).