From: Michael Snyder <Michael.Snyder@access-company.com>
To: Jason Molenda <jmolenda@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] set debug mi
Date: Thu, 12 Apr 2007 00:51:00 -0000 [thread overview]
Message-ID: <1176339097.26620.55.camel@svmsnyderlnx.palmsource.com> (raw)
In-Reply-To: <2FBCCFDF-95E9-43E5-88A3-F2B26EDC5CE0@apple.com>
On Wed, 2007-04-11 at 17:42 -0700, Jason Molenda wrote:
> On Apr 11, 2007, at 4:50 PM, Michael Snyder wrote:
>
> > Anybody think this is useful?
>
> We do something similar at Apple but we have our front-end program
> deal with it. The UI has a preference to save the mi log to a file;
> it saves all communication between gdb and the FE to that file. It's
> invaluable for debugging bug reports - it's invariably the first thing
> we ask for when someone reports a bug against our debugger. Besides
> pointing the finger at either gdb or the front-end it has the benefit
> of showing exactly what commands were sent to the debugger, instead of
> relying on the user's memory of the same.
>
> I think the approach of having all I/O between the debugger and the FE
> saved is superior but having something like this built in to gdb could
> be helpful for people who can't do that easily in the FE.
Eclipse also has a similar option. I just thought it might be
handy to have the facility on the gdb end as well. By obvious
analogy with "debug remote".
next prev parent reply other threads:[~2007-04-12 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 23:51 Michael Snyder
2007-04-12 0:31 ` Nick Roberts
2007-04-12 0:53 ` Michael Snyder
2007-04-12 0:42 ` Jason Molenda
2007-04-12 0:51 ` Michael Snyder [this message]
2007-04-12 6:40 ` Vladimir Prus
2007-04-12 15:34 ` Daniel Jacobowitz
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=1176339097.26620.55.camel@svmsnyderlnx.palmsource.com \
--to=michael.snyder@access-company.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jmolenda@apple.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