This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: industrial use of 'record' and replay.


> 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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]