From: pfee@talk21.com
To: Joel Brobecker <brobecker@adacore.com>, Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Enhancement - show old and new thread info when switching during debugging
Date: Sat, 30 Jul 2011 12:40:00 -0000 [thread overview]
Message-ID: <1312025974.40998.YahooMailRC@web86705.mail.ird.yahoo.com> (raw)
In-Reply-To: <20110730024405.GJ5177@adacore.com>
> > Joel> Isn't that information already present in the previous "[Switching to
> > Joel> thread ...]" message?
> >
> > We can always add an option, like "set print thread previous on" to
> > control the output.
>
> Generally speaking, I prefer to avoid introducing options unless
> really necessary. In this particular case, it sounds like the most
> convenient way of solving the problem is to have a convenience
> variable. And it sounds like the only reason why Paul hasn't looked
> at the implementation yet is due to lack of familiarity with this
> code?
>
> % grep '"bpnum"' *.c
> breakpoint.c: set_internalvar_integer (lookup_internalvar ("bpnum"),
>num);
>
> So, I would think that adding something similar in
> thread.c:switch_to_thread would do the job.
>
I'll look into convenience variables. Since it saves translating LWPs into GDB
thread IDs and avoids output "noise", I think it's the better than my patch.
I'll warn you in advance it might be a week until I develop something as I may
be without Internet access for a while.
Thanks for the tips on where to look next.
--
Paul
next prev parent reply other threads:[~2011-07-30 11:39 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
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 [this message]
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=1312025974.40998.YahooMailRC@web86705.mail.ird.yahoo.com \
--to=pfee@talk21.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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