From: Toby Haynes <thaynes@ca.ibm.com>
To: gdb@sourceware.org
Subject: Re: industrial use of 'record' and replay.
Date: Tue, 09 Jun 2009 19:41:00 -0000 [thread overview]
Message-ID: <OF7F3FA209.A7FB1B89-ON852575CB.006FC945-852575D0.006C03D0@ca.ibm.com> (raw)
In-Reply-To: <5cfa99000906021850s5bdb4a94t8bdea5b254936ddf@mail.gmail.com>
> Edward Peschko <horos11@gmail.com>
> What I want to do is record a program, but not necessarily have to
replay it
> from the start of its recording - ie: have the system automatically
> take 'snapshots'
> of the state at given intervals, and then have the ability to replay
> from any given
> snapshot.
Picking up on this, is it possible to configure the record to use a
circular buffer, effectively recording only the most recent events? Even
better if we can specify the size or number of events on that buffer.
If, for example, I wanted to use this to debug a crash problem in a large
project (where large implies more than 1Gb of source code, with multiple
processes and threads), being able to set reasonable bounds for recording
will be critical to make use of this facility. Doubly so in scenarios
which fail stress tests after more than 24 hours of operation. Being able
to rewind from the crash point to see precisely what lead to the crash
would be a killer feature, with huge time savings.
Thanks,
Toby Haynes
next prev parent reply other threads:[~2009-06-09 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 21:49 Edward Peschko
2009-06-03 1:20 ` Marc Khouzam
2009-06-03 1:50 ` Edward Peschko
2009-06-09 19:41 ` Toby Haynes [this message]
2009-06-11 1:42 ` Hui Zhu
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=OF7F3FA209.A7FB1B89-ON852575CB.006FC945-852575D0.006C03D0@ca.ibm.com \
--to=thaynes@ca.ibm.com \
--cc=gdb@sourceware.org \
/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