From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sourceware.org, Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: [MI] enabling non-stop mode
Date: Sun, 27 Apr 2008 09:09:00 -0000 [thread overview]
Message-ID: <18451.45027.743862.885534@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200804262216.16948.vladimir@codesourcery.com>
> Probably, we can extend this to enable feature that are not MI proper,
> say:
>
> (gdb) -list-features
> ^done,features=[....,"non-stop",....]
> (gdb) -enable-feature non-stop
> ^done
>
> 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"?
--
Nick http://www.inet.net.nz/~nickrob
WARNING: multiple messages have this Message-ID
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sourceware.org, Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: [MI] enabling non-stop mode
Date: Sun, 27 Apr 2008 06:24:00 -0000 [thread overview]
Message-ID: <18451.45027.743862.885534@kahikatea.snap.net.nz> (raw)
Message-ID: <20080427062400.R5VLLToppD6312ySJlMguWcUsZa5qlCdRf60VVo9uxo@z> (raw)
In-Reply-To: <200804262216.16948.vladimir@codesourcery.com>
> Probably, we can extend this to enable feature that are not MI proper,
> say:
>
> (gdb) -list-features
> ^done,features=[....,"non-stop",....]
> (gdb) -enable-feature non-stop
> ^done
>
> 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"?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-27 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:19 Vladimir Prus
2008-04-27 9:09 ` Nick Roberts [this message]
2008-04-27 6:24 ` Nick Roberts
2008-04-27 19:17 ` Vladimir Prus
2008-04-28 0:15 ` Nick Roberts
2008-04-28 14:20 ` Pedro Alves
2008-05-02 0:25 ` Daniel Jacobowitz
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=18451.45027.743862.885534@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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