From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -stack-select-frame
Date: Thu, 16 Jun 2005 06:41:00 -0000 [thread overview]
Message-ID: <17073.5179.249482.402135@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050616044209.GA5907@nevyn.them.org>
> - You're changing the behavior of a command; do people use this
> command? Are you confident that they will handle the new output
> gracefully?
I'm not aware of anyone using this command - I don't see how they currently
could really. I think its less likely to break existing behaviour than this
change:
2005-05-17 Daniel Jacobowitz <dan@codesourcery.com>
Dennis Brueni <dennis@slickedit.com>
* stack.c (print_frame): In MI mode, output a fullname attribute
with the stack frame.
which must change the output for every frontend using MI.
I don't see how MI can evolve without changing its behaviour. If it is
significantly different presumably a new level can be added as before.
> - Please, let's not add new MI features without matching testcases.
I'll be happy to add testcases if there is a likelihood that my patch will be
approved.
> > ! ^done,frame=@{level="2",addr="0x000107a4",func="foo",
> > ! file="recursive2.c",fullname="/home/foo/bar/devo/myproject/recursive2.c",line=line="14"@},
>
> The double line= is a typo, right?
I've just copied it from another part of the manual. In the node
"GDB/MI Command Description Format" it says:
Manual> Note the the line breaks shown in the examples are here only for
Manual> readability. They don't appear in the real output.
Nick
next prev parent reply other threads:[~2005-06-16 6:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 3:36 Nick Roberts
2005-06-16 4:42 ` Daniel Jacobowitz
2005-06-16 6:41 ` Nick Roberts [this message]
2005-06-16 13:21 ` Daniel Jacobowitz
2005-06-16 22:58 ` Nick Roberts
2005-06-16 23:20 ` Bob Rossi
2005-06-16 23:47 ` Daniel Jacobowitz
2005-06-17 3:07 ` Nick Roberts
2005-06-17 3:21 ` Daniel Jacobowitz
2005-06-17 7:37 ` Nick Roberts
2005-06-17 10:15 ` Eli Zaretskii
2005-06-17 13:33 ` Daniel Jacobowitz
2005-06-18 8:56 ` Eli Zaretskii
2005-06-17 9:55 ` Eli Zaretskii
2005-06-17 9:46 ` Eli Zaretskii
2005-06-16 18:23 ` Eli Zaretskii
2005-06-16 20:15 ` Jason Molenda
2005-06-16 23:04 ` Nick Roberts
2005-06-16 23:30 ` Jason Molenda
2005-06-17 7:22 ` Nick Roberts
2005-06-17 13:30 ` Daniel Jacobowitz
2005-06-17 19:48 ` Jason Molenda
2005-06-17 22:35 ` Stan Shebs
2005-06-17 22:59 ` Daniel Jacobowitz
2005-06-17 23:31 ` Nick Roberts
[not found] <1119003319.5434.ezmlm@sources.redhat.com>
2005-06-17 17:45 ` Jim Ingham
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=17073.5179.249482.402135@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.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