From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ian Lance Taylor <ian@airs.com>,
michsnyd@cisco.com, gdb@sources.redhat.com, shebs@apple.com
Subject: Re: Using reverse execution
Date: Wed, 21 Sep 2005 04:03:00 -0000 [thread overview]
Message-ID: <20050921040154.GA7040@nevyn.them.org> (raw)
In-Reply-To: <u4q8fhywx.fsf@gnu.org>
On Wed, Sep 21, 2005 at 06:39:42AM +0300, Eli Zaretskii wrote:
> > Cc: gdb@sources.redhat.com, shebs@apple.com
> > From: Ian Lance Taylor <ian@airs.com>
> > Date: 20 Sep 2005 16:13:55 -0700
> >
> > There is probably some cool use for which tracepoints are the
> > obvious right answer, but I don't know what it is.
>
> In native debugging, tracepoints would be very useful to debug a
> real-time program, or, more generally, a program where timing issues
> are crucial to its correct operation. With such programs, normal GDB
> usage disrupts the program operation and might even cause the program
> to fail in ways that are unrelated to the bug you are looking for.
Yes - and I've definitely tried to debug programs using GDB where this
would have been helpful. E.G. when working on the MIPS port of NPTL.
I ended up doing the manual equivalent using printf, but printf can
actually be much higher overhead than in-memory tracepointing, and
recompiling libc every time I needed to change the debugging output got
to be a bit of a drag.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-21 4:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 22:56 Michael Snyder
2005-09-20 23:14 ` Ian Lance Taylor
2005-09-21 3:40 ` Eli Zaretskii
2005-09-21 4:00 ` Ian Lance Taylor
2005-09-21 17:52 ` Eli Zaretskii
2005-09-21 20:37 ` Michael Snyder
2005-09-24 0:46 ` Stan Shebs
2005-09-24 1:10 ` Michael Snyder
2005-09-24 10:05 ` Eli Zaretskii
2005-09-27 22:00 ` Jim Blandy
2005-09-21 4:03 ` Daniel Jacobowitz [this message]
2005-09-21 16:56 ` Paul Gilliam
2005-09-23 23:44 ` Stan Shebs
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 23:11 Michael Snyder
2005-09-24 0:07 ` Stan Shebs
2005-09-20 22:47 Michael Snyder
2005-09-13 1:17 Stan Shebs
2005-09-13 3:43 ` Eli Zaretskii
2005-09-14 0:36 ` Stan Shebs
2005-09-14 3:42 ` Eli Zaretskii
2005-09-14 22:34 ` Stan Shebs
2005-09-15 3:37 ` Eli Zaretskii
2005-09-15 5:36 ` Stan Shebs
2005-09-15 15:14 ` Eli Zaretskii
2005-09-15 18:02 ` Jason Molenda
2005-09-15 20:12 ` Stan Shebs
2005-09-16 10:42 ` Eli Zaretskii
2005-09-16 14:00 ` Stan Shebs
2005-09-16 16:22 ` Eli Zaretskii
2005-09-16 18:03 ` Stan Shebs
2005-09-16 20:50 ` Eli Zaretskii
2005-09-23 23:20 ` Stan Shebs
2005-09-16 17:50 ` Ian Lance Taylor
2005-09-16 10:43 ` Eli Zaretskii
2005-09-13 18:11 ` Min Xu (Hsu)
2005-09-13 22:01 ` Jim Blandy
2005-09-14 0:42 ` Stan Shebs
2005-09-16 12:03 ` Ramana Radhakrishnan
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=20050921040154.GA7040@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ian@airs.com \
--cc=michsnyd@cisco.com \
--cc=shebs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).