This is the mail archive of the
mailing list for the GDB project.
Re: [MI] enabling non-stop mode
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb at sourceware dot org, Marc Khouzam <marc dot khouzam at ericsson dot com>
- Date: Sun, 27 Apr 2008 10:42:43 +1200
- Subject: Re: [MI] enabling non-stop mode
- References: <firstname.lastname@example.org>
> Probably, we can extend this to enable feature that are not MI proper,
> (gdb) -list-features
> (gdb) -enable-feature non-stop
> The only issue here is that non-stop mode availability in general
> depends on the target, so maybe we should have a separate commands
> to list "target" feature and then enable target features?
Why not just use -gdb-set?
maint set linux-async --> set linux-async --> -gdb-set linux-async
maint set non-stop --> set non-stop --> -gdb-set non-stop
I thought the idea of -list-features was to give the frontend a simple means of
finding out which MI commands a version of Gdb will accept. Why would a
frontend want to do "-disable-feature frozen-varobjs"?