From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2975 invoked by alias); 24 Mar 2005 23:59:37 -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 2939 invoked from network); 24 Mar 2005 23:59:31 -0000 Received: from unknown (HELO calvin.codito.co.in) (220.225.32.98) by sourceware.org with SMTP; 24 Mar 2005 23:59:31 -0000 Received: from [192.168.100.52] (arnor.codito.co.in [192.168.100.52]) by calvin.codito.co.in (8.12.10/8.12.10) with ESMTP id j2ONwO89025543; Fri, 25 Mar 2005 05:28:25 +0530 Message-ID: <4243541A.2010300@codito.com> Date: Thu, 24 Mar 2005 23:59:00 -0000 From: Ramana Radhakrishnan User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) MIME-Version: 1.0 To: james osburn CC: gdb@sources.redhat.com Subject: Re: tracing ( was Re: what are gdbstubs?) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-03/txt/msg00231.txt.bz2 james osburn wrote: > no actually i am very very new to using > gdb so no i didnt know about scripting the > break points. how does that work? > jim Its like this . Look at the commands command for gdb . So at each program point if you specify the variables of interest for you, you could generate the following set of commands for the same. break commands > p > p $eax > p $ebx > end etc. or you could use the display command for each of the variables that you wish to see and then single step as many instructions / source lines as you want. cheers Ramana -- Ramana Radhakrishnan GNU Tools codito ergo sum (www.codito.com)