This is the mail archive of the
mailing list for the GDB project.
RE: MI non-stop interface details
- From: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- To: "Vladimir Prus" <vladimir at codesourcery dot com>, "Doug Evans" <dje at google dot com>
- Cc: <gdb at sourceware dot org>, "Pawel Piech" <pawel dot piech at windriver dot com>
- Date: Tue, 29 Apr 2008 14:50:34 -0400
- Subject: RE: MI non-stop interface details
> > - CLI users won't see the thread switches
> > IOW GDB won't switch the current thread on the user, right? [just
> > want to understand what you're saying, not to suggest a preference,
> > per se]
> Yes. GDB will switch its internal "current thread" when processing event,
> but it will switch it back to whatever user has last set before processing
> next user command.
I think this is great.
> > 5. Introduce new command -query-feature (?) [assuming it's not there
> > already, I don't know]
> That will report if a feature is enabled or not? We don't have it (just like
> we don't have -enable-feature yet). I'm thinking, though, that for all features
> we'd document if it's enabled by default, or not, so this command might not be
> a big use.
You may be right that such a command may not prove very useful, but in my experience,
if you can modify a setting, it is always good to have a way to report its current state.