Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [RCF 0/6 V2] MI notification of command option change
@ 2012-07-27 15:23 Yao Qi
  2012-07-27 15:23 ` [PATCH 6/6] code indentation Yao Qi
                   ` (6 more replies)
  0 siblings, 7 replies; 18+ messages in thread
From: Yao Qi @ 2012-07-27 15:23 UTC (permalink / raw)
  To: gdb-patches

Hi,
This is the V2 of this patch set.  Compared with V1, some decisions
are made:

  1.  Keep the command-registration functions unchanged (discard
my xxx_wit_notif functions).
  2.  Don't emit option change of all gdb commands.  We have to
set 'reporting' commands via function 'set_cmd_notify', otherwise
commands are still 'no-reporting'.  I believe that frontends will
request more and more options changes, but changes of some gdb
options are useless to frontends.  It is noisy to send all option
changes.

Tom and Pedro's review comments are addressed in this version.


^ permalink raw reply	[flat|nested] 18+ messages in thread
* [RFC 0/6] MI notification of command option change
@ 2012-07-24 16:11 Yao Qi
  2012-07-24 16:11 ` [PATCH 1/6] new observer command_option_changed Yao Qi
  0 siblings, 1 reply; 18+ messages in thread
From: Yao Qi @ 2012-07-24 16:11 UTC (permalink / raw)
  To: gdb-patches

When Eclipse connects to GDB through MI, user is still abel to
type command in console (or telnet session), so the state of GDB
may be changed while Eclipse is not aware of.  GDB is lack of
notifications to MI front end and/or telnet session when the
internal state of GDB is changed (eg. changed by some 'set foo bar'
commands or tracepoint is downloaded).

This patch series is to address the problem that caused by
command 'set foo bar'.  When user types some interesting commands
in console, GDB will send MI notifications about the command
option changes.  The following patch series will address the
problem caused by other aspects in the future.  In this way,
Eclipse is aware of the change of GDB state, and refresh or
update itself accordingly.

Patch 1/6 - 3/6 are about the new observer 'command_option_changed'
and new MI notification '=option-changed' when observer is notified.
Patch 4/6 - 6/6 are about registering three types of command
respectively.  Three commands will send MI notifications if their
option is changed.  There are more than three commands that can
change the state of GDB, but these three are reprsentives of
them.  The rest of commands can be easily changed to sending
MI notifications.

Regression tested on x86_64 native/gdbserver.


^ permalink raw reply	[flat|nested] 18+ messages in thread

end of thread, other threads:[~2012-07-27 17:56 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-27 15:23 [RCF 0/6 V2] MI notification of command option change Yao Qi
2012-07-27 15:23 ` [PATCH 6/6] code indentation Yao Qi
2012-07-27 15:23 ` [PATCH 3/6] notify in enum_cmd and scheduler-locking Yao Qi
2012-07-27 15:23 ` [PATCH 1/6] new observer command_option_changed Yao Qi
2012-07-27 17:56   ` Tom Tromey
2012-07-27 15:23 ` [PATCH 5/6] notify in string_cmd and trace-notes Yao Qi
2012-07-27 15:23 ` [PATCH 4/6] notify in boolean_cmd and circular-trace-buffer Yao Qi
2012-07-27 15:23 ` [PATCH 2/6] attach to command_option-changed observer Yao Qi
2012-07-27 17:20   ` Tom Tromey
2012-07-27 17:44   ` Tom Tromey
2012-07-27 17:07 ` [RCF 0/6 V2] MI notification of command option change Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2012-07-24 16:11 [RFC 0/6] " Yao Qi
2012-07-24 16:11 ` [PATCH 1/6] new observer command_option_changed Yao Qi
2012-07-24 20:39   ` Tom Tromey
2012-07-25  3:56     ` Yao Qi
2012-07-25 14:44       ` Tom Tromey
2012-07-26 15:21         ` Pedro Alves
2012-07-25 14:32   ` Tom Tromey
2012-07-26  8:55     ` Yao Qi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox