From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/MI] Event Records vs Commands
Date: Sat, 15 Jun 2002 19:01:00 -0000 [thread overview]
Message-ID: <3D0BF171.2030409@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0206132206350.19373-100000@makita.cygnus.com>
> Hi,
>
> This is the promised gdbmi.texinfo proposal that I referred to in:
>
> http://sources.redhat.com/ml/gdb/2002-06/msg00106.html
>
> This patch formalizes events in MI. Specifically, I propose to whack
> notify-async-output from aync-record and add event-record to
> out-of-band-record.
Breakpoint events can occure ``asynchronously'': a shared library load
might trigger the setting of a breakpoint; a user's breakpoint commands
might change the state of a breakpoint and then continue.
Hence, as far as I can tell you just want to ``notify-async-output''.
> I've modified all the breakpoint command examples to reflect the fact that
> breakpoint commands will no longer print information about the breakpoint.
> Instead this information is retrieved from the event. For example:
>
> - old way
> (gdb)
> -break-insert main
> ^done,bkpt={number="1",addr="0xdeadbeef",file="main.c",line="5"}
> (gdb)
>
> - new way
> (gdb)
> -break-insert main
> =breakpoint-create,number="1"
> (gdb)
I believe this is wrong. There should still be a ``^done''.
> -break-info 1
> ^done,BreakpointTable={...}
> I have completed the changes to MI to accomplish this, and I will submit
> these patches once this is all approved. I plan to check this all into my
> interpreter branch (kseitz_interps-20020528-branch) until everything
> is finalized. I will then migrate the whole (approved) thing into cvs
> head.
Keep in mind that the examples are lifted from the testsuite.
Given breakpoint output appears everywhere in the testsuite, the import
is going to be a little large. There should still be a few things that
can be cherry picked though - some of the testsuite shuffle for instance.
> @example
> -> -symbol-file xyz.exe
> ! <- *breakpoint,nr="3",address="0x123",source="a.c:123"
> <- (@value{GDBP})
> @end example
>
> --- 395,402 ----
>
> @example
> -> -symbol-file xyz.exe
> ! <- =breakpoint-create,number="3"
> ! <- ^done
> <- (@value{GDBP})
> @end example
If breakpoint-create included complete breakpoint information an
additional roundtrip could be avoided. Is this significant? I suspect
this is a question for some of the apple hackers as they would have a
better feel for how critical this one is :-)
Andrew
next prev parent reply other threads:[~2002-06-16 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 22:24 Keith Seitz
2002-06-15 10:33 ` Eli Zaretskii
2002-06-15 11:46 ` Andreas Schwab
2002-06-15 19:01 ` Andrew Cagney [this message]
2002-06-15 19:10 ` Andrew Cagney
2002-06-18 11:34 ` Keith Seitz
2002-06-18 13:43 ` Eli Zaretskii
2002-06-25 20:17 ` Andrew Cagney
2002-06-17 10:25 ` Keith Seitz
2002-06-17 11:28 ` 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=3D0BF171.2030409@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.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