From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>,
"'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: RE: [MI] -thread-select using the --thread option
Date: Fri, 12 Feb 2010 14:54:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC515FB3DAA7@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <hl3aid$g3t$2@ger.gmane.org>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: Friday, February 12, 2010 5:30 AM
> To: gdb@sources.redhat.com
> Subject: Re: [MI] -thread-select using the --thread option
>
> Marc Khouzam wrote:
>
> > Hi,
> >
> > I just realized that DSF-GDB (with GDB 7.0), when forced to
> use -thread-select,
> > is adding the --thread option to it. So I see
> >
> > -thread-select --thread 1 1
> >
> > This will happen before using a CLI command ('jump'), for example.
> >
> > I'm assuming I should just turn off the use of the --thread
> option for
> > -thread-select. I just wanted to check with you experts if it truly
> > is that simple.
>
> Well, the officially blessed way is to never use -thread-select in
> the first place ;-) If you are going to use it, then well, omitting
> --thread seems reasonable.
Thanks
Whenever I use an MI command I use --thread instead of -thread-select,
but when I have to use a CLI command I have to use -thread-select.
But that does not happen very often (actually, I don't have an
example anymore, since I noticed that -exec-jump exists)
next prev parent reply other threads:[~2010-02-12 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 20:27 Marc Khouzam
2010-02-12 10:30 ` Vladimir Prus
2010-02-12 14:54 ` Marc Khouzam [this message]
2010-02-12 14:57 ` Vladimir Prus
2010-02-12 15:01 ` Marc Khouzam
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=F7CE05678329534C957159168FA70DEC515FB3DAA7@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sources.redhat.com \
--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