From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: Nick Roberts <nick@nick.uklinux.net>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] implements MI "-file-list-exec-sections" (updated)
Date: Fri, 07 May 2004 01:19:00 -0000 [thread overview]
Message-ID: <409A9BD3.6050803@gnu.org> (raw)
In-Reply-To: <20040502132531.GB1487@white>
> On Sat, May 01, 2004 at 01:07:44PM +0100, Nick Roberts wrote:
>
>>>
>>> > I think everyone agrees, changing the CLI would be the worst possible
>>> > thing GDB could do.
>>>
>>> I'm not sure if thats true, I was just talking about timing. Its probably
>>> not reasonable or even realistic to insist that CLI output never changes.
>
>
> Well, over time, I can see the CLI changing. However, I would expect
> that to happen after at least one open source project implemented the MI
> front end (Don't say eclipse, they use a hybrid approach) and the MI
> API was considered stable and capable of doing everything that could
> be done from the CLI.
Regardless of MI, the CLI is going to evolve. This is because the
current implementation is limiting GDB's functionality.
A few simple examples:
- signal backtraces. They currently look something like:
0x1234 in foo
<signal handler called>
0x456 in bar
but are about to be changed to:
0x1234 in foo
0x785 in <signal trampoline>
0x456 in bar
This comes hand-in-hand with the raised expectation that operations such
as "stepi"ing through a trampoline work (previously it was luck,
typically bad :-). For the user this is all good, but I bet there's a
CLI parsing gui out there that breaks - oops.
- N:M breakpoints
Again, the user will easily adapt.
Andrew
next prev parent reply other threads:[~2004-05-07 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 21:54 Nick Roberts
2004-05-01 4:09 ` Bob Rossi
2004-05-01 12:08 ` Nick Roberts
2004-05-02 13:25 ` Bob Rossi
2004-05-07 1:19 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 21:56 Stefan Weyergraf
2004-04-22 22:22 ` Bob Rossi
2004-04-22 23:31 ` Stefan Weyergraf
2004-04-28 21:51 ` Andrew Cagney
2004-05-07 1:20 ` Andrew Cagney
2004-05-06 22:07 ` Stefan Weyergraf
2004-05-12 20:14 ` 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=409A9BD3.6050803@gnu.org \
--to=cagney@gnu.org \
--cc=bob@brasko.net \
--cc=gdb-patches@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