From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Report current thread in -thread-list-ids output
Date: Fri, 30 Jan 2009 21:10:00 -0000 [thread overview]
Message-ID: <200901301719.35433.pedro@codesourcery.com> (raw)
In-Reply-To: <200901301939.43053.vladimir@codesourcery.com>
On Friday 30 January 2009 16:39:42, Vladimir Prus wrote:
>
> This patch makes the MI -thread-list-ids report the current thread.
> It is advantageous for a frontend like Eclipse, that does not report
> any details about a thread whatsoever except for the id, and whether
> a thread is selected. If -thread-list-ids reports current thread, then
> Eclipse can use -thread-list-ids as opposed to 'info thread', and be
> a little bit faster.
>
> The change in thread.c actually touches MI-only function, so I assume
> I'm free to make this change.
In any case, it looks good to me. This fixes PR8145,
<http://sourceware.org/bugzilla/show_bug.cgi?id=8145> .
> Eli, does the doc change look good?
--
Pedro Alves
WARNING: multiple messages have this Message-ID
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Report current thread in -thread-list-ids output
Date: Fri, 30 Jan 2009 20:36:00 -0000 [thread overview]
Message-ID: <200901301719.35433.pedro@codesourcery.com> (raw)
Message-ID: <20090130203600.bUWyZs4OZ1jpc3RG3aD-rjto8-qqJnescjtLc7nHMmQ@z> (raw)
In-Reply-To: <200901301939.43053.vladimir@codesourcery.com>
On Friday 30 January 2009 16:39:42, Vladimir Prus wrote:
>
> This patch makes the MI -thread-list-ids report the current thread.
> It is advantageous for a frontend like Eclipse, that does not report
> any details about a thread whatsoever except for the id, and whether
> a thread is selected. If -thread-list-ids reports current thread, then
> Eclipse can use -thread-list-ids as opposed to 'info thread', and be
> a little bit faster.
>
> The change in thread.c actually touches MI-only function, so I assume
> I'm free to make this change.
In any case, it looks good to me. This fixes PR8145,
<http://sourceware.org/bugzilla/show_bug.cgi?id=8145> .
> Eli, does the doc change look good?
--
Pedro Alves
next prev parent reply other threads:[~2009-01-30 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:43 Vladimir Prus
2009-01-30 21:10 ` Pedro Alves [this message]
2009-01-30 20:36 ` Pedro Alves
2009-01-30 21:51 ` Eli Zaretskii
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=200901301719.35433.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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