Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: pfee@talk21.com
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Enhancement - show old and new thread info when switching during debugging
Date: Fri, 29 Jul 2011 16:33:00 -0000	[thread overview]
Message-ID: <1311955683.74296.YahooMailRC@web86704.mail.ird.yahoo.com> (raw)
In-Reply-To: <20110729155438.GH5177@adacore.com>

> > The following patch is also attached to bug 13042.
> > http://sourceware.org/bugzilla/show_bug.cgi?id=13042
> > 
> > It  gives the user info about the thread they're switching from in
> > addition  to that which they're switching to.  This is useful if the
> > switch  was not intended and they wish to continue debugging the old
> >  thread.
> 
> Isn't that information already present in the previous  "[Switching to
> thread ...]" message?

I've copied output from GDB 7.3 before and after my patch into the bug report 
along with some notes on the implementation.

Without the patch the user is told what thread they're switching to, but not 
what thread they're switching from, e.g.


[Switching to Thread 0x7ffff7fd6700 (LWP 4267)]
In a program with numerous threads, the old thread may be the one the user is 
interested it.  They may not have wanted to switch, but by chance the new thread 
has hit a breakpoint.  By giving information about what thread we're switching 
away from, it becomes easier for the user to switch back to that thread and 
ignore the accidental thread switch.

Example of new output:

[Switching from Thread 0x7ffff7fd8740 (LWP 4279) to Thread 0x7ffff7fd6700 (LWP 
4282)]Thanks,
Paul


  reply	other threads:[~2011-07-29 16:08 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 [this message]
2011-07-29 17:38     ` Joel Brobecker
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=1311955683.74296.YahooMailRC@web86704.mail.ird.yahoo.com \
    --to=pfee@talk21.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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