From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: Do we need MI -inferior-select
Date: Wed, 11 Aug 2010 13:03:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5716DAC203@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5716DAC1F8@EUSAACMS0703.eamcs.ericsson.se>
Sigh...
Forget it, I believe I can use:
-interpreter-exec --thread-group <groupId> console <cli command>
I keep forgetting about this one. Sorry.
Marc
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Marc Khouzam
> Sent: Wednesday, August 11, 2010 8:59 AM
> To: 'gdb@sourceware.org'
> Subject: Do we need MI -inferior-select
>
> Hi,
>
> CLI has an 'inferior' command to switch to a different inferior.
> MI does not have such a command. Instead, if I understand correctly,
> MI provides a global --thread-group option that allows to specify
> the inferior, for each MI command. This is very nice.
>
> Howver, I'm worried about CLI commands that don't have an MI
> equivalent.
> How would I select the inferior for those commands?
> I don't have an actual example yet, but with 7.2 almost ready,
> I thought it was worth asking if we should add a new MI command
> for the CLI 'inferior'.
>
> Normally, I could simply use the CLI 'inferior' command if there
> is no MI equivalent, but I've noticed that the inferior ID used by
> CLI is not the same as the groupId used by MI. Therefore, to use
> 'inferior' the frontend would need to be able to map the groupId
> to a CLI inferiorId, which I'm not sure will necessarily be easy.
>
> I'm ready to write a patch for -inferior-select, if it is agreed
> that it is needed.
>
> Thanks
>
> Marc
>
>
>
>
>
prev parent reply other threads:[~2010-08-11 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 12:59 Marc Khouzam
2010-08-11 13:03 ` Marc Khouzam [this message]
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=F7CE05678329534C957159168FA70DEC5716DAC203@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
/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