From: Joel Brobecker <brobecker@adacore.com>
To: pfee@talk21.com
Cc: gdb-patches@sourceware.org
Subject: Re: Enhancement - show old and new thread info when switching during debugging
Date: Fri, 29 Jul 2011 17:38:00 -0000 [thread overview]
Message-ID: <20110729161711.GI5177@adacore.com> (raw)
In-Reply-To: <1311955683.74296.YahooMailRC@web86704.mail.ird.yahoo.com>
> I've copied output from GDB 7.3 before and after my patch into the bug
> report along with some notes on the implementation.
I think I understand what you are trying to say. What I am saying is
that you can find which thread you switched from, by going up the
debugger output until you find a "[Switching to Thread ...]" message.
So, the information is already there. I agree it's not ultra convenient,
but I personally think it's better than your approach (the new message
becomes way to long, IMO).
In your case, if going up the output is not good enough, I would
suggest two alternative solutions, in order of preference:
- Have GDB maintain variable $old_thread or $prev_thread that
you can then use to switch to the previous thread;
(gdb) thread $old_thread
would return you to the previous thread before the switch.
- At least print the new thread ID first;
--
Joel
next prev parent reply other threads:[~2011-07-29 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:29 pfee
2011-07-29 16:01 ` Joel Brobecker
2011-07-29 16:33 ` pfee
2011-07-29 17:38 ` Joel Brobecker [this message]
2011-07-29 17:47 ` pfee
2011-07-29 20:40 ` Philippe Waroquiers
2011-07-30 2:44 ` Tom Tromey
2011-07-30 11:39 ` Joel Brobecker
2011-07-30 11:44 ` Pedro Alves
2011-07-30 14:12 ` pfee
2011-08-08 11:35 ` pfee
2011-08-08 15:07 ` Pedro Alves
2011-08-08 15:20 ` pfee
2011-08-09 15:25 ` pfee
2011-08-10 15:10 ` Pedro Alves
2011-08-16 16:01 ` pfee
2011-07-30 12:40 ` pfee
2011-07-30 11:32 ` Tom Tromey
2011-07-30 22:07 ` Jan Kratochvil
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=20110729161711.GI5177@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pfee@talk21.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