From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25936 invoked by alias); 18 May 2004 17:04:25 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25908 invoked from network); 18 May 2004 17:04:23 -0000 Received: from unknown (HELO ptb-relay03.plus.net) (212.159.14.214) by sourceware.org with SMTP; 18 May 2004 17:04:23 -0000 Received: from [81.174.168.250] (helo=avocado) by ptb-relay03.plus.net with smtp (Exim) id 1BQ80t-000HCe-37 for gdb@sources.redhat.com; Tue, 18 May 2004 17:04:23 +0000 From: "Chris January" To: Subject: RE: GDB as a program analyzer - some thoughts Date: Tue, 18 May 2004 17:04:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <40AA23FD.6040103@lifl.fr> X-SW-Source: 2004-05/txt/msg00124.txt.bz2 > This post deals about using GDB for non-debugging purposes, I hope it's > not offtopic. I'm also hoping to find some people interested in the same > matters than I to discuss about how GDB could be improved for analysis > purposes. See: http://www.argreenhouse.com/papers/hira/spe93.pdf for a program trace/dynamic analysis tool built on top of gdb and gcc. I'm currently working on a program tracing tool for i386 that uses Valgrind and GDB for my final year project. It should allow you to query program traces using SQL. Example: set filter {x>5} history or some similar syntax. would show you all the places when (and where) the variable x (when in scope) had a value greater than 5. Feel free to mail me off list if you want to discuss this kind of thing any further. Regards, Chris