From: Andrew Cagney <cagney@gnu.org>
To: George Anzinger <george@mvista.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Eli Zaretskii <eliz@elta.co.il>,
gdb@sources.redhat.com
Subject: Re: Making "info thread" sane
Date: Fri, 12 Mar 2004 21:33:00 -0000 [thread overview]
Message-ID: <40522C95.7060900@gnu.org> (raw)
In-Reply-To: <40510325.4070101@mvista.com>
>>
>> > 2) I would like to have the result of the "ThreadExtraInfo" on the same line (as the info thread command does).
>>
>> Can you post the output so we can see exactly what you mean here?
>
>
> I haven't got it all working as yet, but the "thread apply all"
> puts out something like:
> Thread 1 (Thread 1):
> for each thread. An option I would like is for this to not have new line so I can add to it, something like:
> Thread 1 (Thread 1): (init) 0xff00....
> and keep it all on one line.
Ah, ulgh. I don't think it should output anything. Something like:
foreach thread $t
end
?
Andrew
next prev parent reply other threads:[~2004-03-12 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040227212301.GC1052@smtp.west.cox.net>
[not found] ` <20040227235059.GG425@elf.ucw.cz>
[not found] ` <403FEA02.6040506@mvista.com>
[not found] ` <200403011454.35346.amitkale@emsyssoft.com>
[not found] ` <4044FEDE.5000105@mvista.com>
[not found] ` <20040302214535.GA24405@nevyn.them.org>
[not found] ` <40450749.7020304@mvista.com>
[not found] ` <20040302221718.GA26931@nevyn.them.org>
2004-03-02 23:15 ` George Anzinger
2004-03-02 23:25 ` Andrew Cagney
2004-03-03 0:14 ` George Anzinger
2004-03-03 6:01 ` Eli Zaretskii
2004-03-03 14:28 ` Daniel Jacobowitz
2004-03-03 15:08 ` Andrew Cagney
2004-03-03 18:40 ` George Anzinger
2004-03-03 18:54 ` Andrew Cagney
2004-03-03 22:04 ` George Anzinger
2004-03-09 1:25 ` Andrew Cagney
2004-03-12 0:24 ` George Anzinger
2004-03-12 21:33 ` Andrew Cagney [this message]
2004-03-22 9:40 ` George Anzinger
2004-04-21 1:30 ` George Anzinger
2004-03-08 19:21 Jim Houston
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=40522C95.7060900@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=george@mvista.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