From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14669 invoked by alias); 9 Jun 2009 19:41:30 -0000 Received: (qmail 14652 invoked by uid 22791); 9 Jun 2009 19:41:28 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_50,SPF_PASS X-Spam-Check-By: sourceware.org Received: from e1.ny.us.ibm.com (HELO e1.ny.us.ibm.com) (32.97.182.141) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 09 Jun 2009 19:41:19 +0000 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e1.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n59JarVh002981 for ; Tue, 9 Jun 2009 15:36:53 -0400 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n59JdvLV253074 for ; Tue, 9 Jun 2009 15:39:57 -0400 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n59JduXC031577 for ; Tue, 9 Jun 2009 15:39:56 -0400 Received: from d25ml01.torolab.ibm.com (d25ml01.torolab.ibm.com [9.26.6.102]) by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n59Jdurv031569 for ; Tue, 9 Jun 2009 15:39:56 -0400 In-Reply-To: <5cfa99000906021850s5bdb4a94t8bdea5b254936ddf@mail.gmail.com> References: <5cfa99000906021448y5a7b4418l8578052bbd79757e@mail.gmail.com> <6D19CA8D71C89C43A057926FE0D4ADAA0786E824@ecamlmw720.eamcs.ericsson.se> <5cfa99000906021850s5bdb4a94t8bdea5b254936ddf@mail.gmail.com> To: gdb@sourceware.org MIME-Version: 1.0 Subject: Re: industrial use of 'record' and replay. X-KeepSent: 7F3FA209:A7FB1B89-852575CB:006FC945; type=4; name=$KeepSent Message-ID: From: Toby Haynes Date: Tue, 09 Jun 2009 19:41:00 -0000 Content-Type: text/plain; charset="US-ASCII" X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00078.txt.bz2 > Edward Peschko > 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