[MI] -thread-select using the --thread option

[MI] -thread-select using the --thread option

[Marc Khouzam]

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.

Of course, I would do the same for the --frame option
and for the -stack-select-frame command.

Thanks

Marc

Re: [MI] -thread-select using the --thread option

[Vladimir Prus]

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.

- Volodya

RE: [MI] -thread-select using the --thread option

[Marc Khouzam]

> -----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)

Re: [MI] -thread-select using the --thread option

[Vladimir Prus]

On Friday 12 February 2010 17:54:44 you wrote:

> 
> > -----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.

Why? I though that:

	-interpreter-exec --thread 1 "cli" "the command"

should work just fine.

- Volodya

RE: [MI] -thread-select using the --thread option

[Marc Khouzam]

> 
> > 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.
> 
> Why? I though that:
> 
> 	-interpreter-exec --thread 1 "cli" "the command"
> 
> should work just fine.

You're right.  I have an outstanding bug to use that format instead.
I had forgotten about it :-O

Thanks