From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [commit] fix for "info threads" printing multiple headers
Date: Tue, 22 Feb 2011 10:04:00 -0000 [thread overview]
Message-ID: <201102220927.10146.pedro@codesourcery.com> (raw)
In-Reply-To: <201102220851.20252.pedro@codesourcery.com>
One think I kept wanting to mention and forgetting, is that the
old version was really ineficient against remote targets,
because for "info threads 1-N", you'd pull the thread
list out of the remote target (update_thread_list) N times!
"set debug remote 1; info threads 1-10000" was fun to watch...
--
Pedro Alves
next prev parent reply other threads:[~2011-02-22 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 1:57 Michael Snyder
2011-02-22 9:17 ` Pedro Alves
2011-02-22 10:04 ` Pedro Alves [this message]
2011-02-22 17:45 ` Tom Tromey
2011-02-22 18:37 ` Michael Snyder
2011-02-22 18:49 ` Pedro Alves
2011-02-22 18:31 ` Michael Snyder
2011-02-22 18:41 ` Pedro Alves
2011-02-22 18:55 ` Michael Snyder
2011-02-22 17:37 ` Tom Tromey
2011-02-22 18:36 ` Michael Snyder
2011-02-22 19:00 ` Tom Tromey
2011-02-22 20:05 ` Michael Snyder
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=201102220927.10146.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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