Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jason Molenda <jmolenda@apple.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: Andrew Cagney <cagney@gnu.org>, Alain Magloire <alain@qnx.com>,
	gdb@sources.redhat.com
Subject: Re: How does GDB/MI give the current frame
Date: Thu, 15 Jul 2004 21:08:00 -0000	[thread overview]
Message-ID: <5420CFB8-D69C-11D8-BBF3-000A9569836A@apple.com> (raw)
In-Reply-To: <28ADB7D6-D69A-11D8-BBF3-000A9569836A@apple.com>


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.
>

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

So the UI knows when the user is resuming the inferior behind its back.


J


  reply	other threads:[~2004-07-15 20:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 22:54 Nick Roberts
2004-06-24 23:17 ` Daniel Jacobowitz
2004-06-26  9:10   ` Nick Roberts
2004-06-26 14:59     ` Daniel Jacobowitz
2004-06-27  2:12     ` Andrew Cagney
2004-06-30 20:47       ` Alain Magloire
     [not found]       ` <200406302047.QAA29956@smtp.ott.qnx.com>
2004-07-02 17:29         ` Nick Roberts
2004-07-08 22:15           ` Andrew Cagney
2004-07-08 23:07             ` Alain Magloire
     [not found]             ` <200407082307.TAA09285@smtp.ott.qnx.com>
2004-07-11 22:49               ` Nick Roberts
2004-07-12 18:30                 ` Alain Magloire
     [not found]                 ` <200407121751.NAA24942@smtp.ott.qnx.com>
2004-07-14  4:00                   ` Nick Roberts
2004-07-11 22:49             ` Nick Roberts
2004-07-12 14:24               ` Andrew Cagney
2004-07-12 20:09                 ` Nick Roberts
2004-07-15 14:48                   ` Andrew Cagney
2004-07-15 19:50                     ` Nick Roberts
2004-07-15 20:19                       ` Jason Molenda
2004-07-15 21:08                         ` Jason Molenda [this message]
2004-07-16 14:12                           ` Alain Magloire
2004-07-16 14:08                         ` Alain Magloire
     [not found]                         ` <200407161404.KAA02192@smtp.ott.qnx.com>
2004-07-18 21:07                           ` Nick Roberts
2004-07-26 21:31                             ` Andrew Cagney
2004-06-25 15:12 ` Andrew Cagney

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=5420CFB8-D69C-11D8-BBF3-000A9569836A@apple.com \
    --to=jmolenda@apple.com \
    --cc=alain@qnx.com \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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