From: Daniel Jacobowitz <drow@mvista.com>
To: Nat Gurumoorthy <natg@ubicom.com>
Cc: gdb@sources.redhat.com
Subject: Re: Proposal for customization of output of "to_pid_to_str" op in remote.c
Date: Tue, 10 Dec 2002 19:04:00 -0000 [thread overview]
Message-ID: <20021211030447.GA32482@nevyn.them.org> (raw)
In-Reply-To: <200212110224.gBB2OMH29101@ubicom.com>
On Tue, Dec 10, 2002 at 06:24:22PM -0800, Nat Gurumoorthy wrote:
> >Daniel Jaccobowitz wrote
> >Let's take a step back. What would you be defining this macro as? What do
> you want besides >"New thread"?
>
> Daniel,
> What I am proposing is that this macro is a call into a print
> function defined in my target-tdep.c file. When I type "info threads"
> this interface is getting invoked and I'd like to print a more
> descriptive string about the various threads running on our hardware.
> Right now it prints it out as
> 8 Thread 6
> Which is quite confusing. (The first number is GDB internal numbering.
> The second number is the thread ID issued in my target) What will change
> is that Thread 6 will become something more descriptive.
The remote protocol allows you to return more information in the stub.
Can you do that instead? See ThreadExtraInfo.
> Ps: Daniel I apologize I you are seeing this for the 3rd time. The first
> 2 times I sent it from a Windows machine and the redhat Mailer barfed.
This one has natg@ as your from address, which bounces...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-11 3:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:24 Nat Gurumoorthy
2002-12-10 18:57 ` Christopher Faylor
2002-12-10 19:04 ` Andrew Cagney
2002-12-10 19:04 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 11:33 Nat Gurumoorthy
2002-12-11 14:55 Nat Gurumoorthy
2002-12-11 14:52 Nat Gurumoorthy
2002-12-11 14:57 ` Daniel Jacobowitz
2002-12-10 16:17 Nat Gurumoorthy
2002-12-10 16:49 ` 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=20021211030447.GA32482@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=natg@ubicom.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