public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: michsnyd@cisco.com, gdb@sources.redhat.com, shebs@apple.com
Subject: Re: Using reverse execution
Date: Wed, 21 Sep 2005 17:52:00 -0000	[thread overview]
Message-ID: <uaci6jole.fsf@gnu.org> (raw)
In-Reply-To: <m3u0gf2hq9.fsf@gossamer.airs.com> (message from Ian Lance Taylor on 20 Sep 2005 20:59:58 -0700)

> Cc: michsnyd@cisco.com, gdb@sources.redhat.com, shebs@apple.com
> From: Ian Lance Taylor <ian@airs.com>
> Date: 20 Sep 2005 20:59:58 -0700
> 
> I would put a logging framework in the program itself.  That's how
> I've debugged this sort of issue in the past, and the logging
> framework generally pays off for itself over time.

We've all used some kind of logging system to debug real-time or near
real-time programs---because that's about the only way to debug them,
if you don't have something like tracepoints.  (Well, there's also
oscilloscope debugging for hard real-time programs, if you know what I
mean ;-)

However, debugging through a logging system is akin to printf
debugging; it has all the same deficiencies: the need to recompile the
program to add logging code, which could cause some hard Heisenbugs to
change behavior or even go away, due to code changes and timing
changes.

> (I had several communicating programs with real time interactions.  I
> arranged for each one to spit out log lines into a separate
> multilog-like program to add timestamps, and then after the fact
> sorted the lines together to see what was happening.)

Yep, been-there-done-that.

> Obviously I'm not saying that tracepoints should be removed or
> anything like that.  I'm just responding to Stan's comment that
> tracepoints have been around for a while and not used, by mentioning
> that I personally never seen any important use for them.

You will find in the archives that I said a few years ago that native
tracepoints is a feature to kill for.  Not surprisingly, at the time I
was working on a large real-time software project.  A sophisticated
logging system, augmented by deliberate abort-core-dump code in
strategic places was the best replacement I came up with.  That was on
an SGI machine that needed to respond to an interrupt and run the
application code that serviced the interrupt within 500 microseconds.
I used a scope to convince myself that this hard real-time requirement
was being met.

  reply	other threads:[~2005-09-21 17:52 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 [this message]
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
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=uaci6jole.fsf@gnu.org \
    --to=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).