This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Jul 15, 2004, at 1:04 PM, Jason Molenda wrote:
For what it's worth, at Apple we've done what Andrew is proposing. Our method spits out a "MI_HOOK_RESULT" notification on the ^done result whenever the console command entered by the user has changed the state in an important way. e.g.
[...]
FWIW, here's the list of notification hooks we currently generate: breakpoint_create, breakpoint_modify, breakpoint_delete, stack_changed, frame_changed, thread_changed.
how about for "set p 3", changing values.
I should add that we also call output_control_change_notification() with "stepping" or "continuing" when the user enters a console command that resumes execution. e.g.
(gdb)
-interpreter-exec console-quoted step
^stepping
^running
(gdb)
*stopped,time=
{wallclock="0.01470",user="0.00635",system="0.00845",start="1089922425 .6
47144",end="1089922425.661845"},reason="end-stepping-range",thread-
id="1"
(gdb)
-interpreter-exec console-quoted continue
~"Continuing.\n"
^continuing
^running
Good !!
Few questions why "console-quoted", what's wrong with "console" or rather
what is -quoted provide more ?
What's "^continuing" ? a way to discovered the type of command enter by the user ?
so "^stepping" for step etc ... is it usefull ?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |