From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22680 invoked by alias); 24 Mar 2005 23:44:44 -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 22106 invoked from network); 24 Mar 2005 23:44:36 -0000 Received: from unknown (HELO calvin.codito.co.in) (220.225.32.98) by sourceware.org with SMTP; 24 Mar 2005 23:44:36 -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 j2ONiQ89025487; Fri, 25 Mar 2005 05:14:26 +0530 Message-ID: <424350D3.5080200@codito.com> Date: Thu, 24 Mar 2005 23:44: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/msg00228.txt.bz2 Hi, > sorry i should have been more specific. > a long long time ago (late 80s) borland > turbo c had a trace mode. it would start > a program and then just step line by > line through the code automatically. > you could control the speed and you > had the ability to see the registers and local > variables that where affected. again > the nice feature was that once this trace > feature was started it needed little user > interaction. i am looking > for some feature similar to that. Ok, you are looking for tracepoints in gdb . Its a similar feature but not totally the same .One needs to specify the tracepoints and the data to be collected. They are not supported with gdbserver AFAIK (of 6.3 vintage) . There have been some recent patches by Nathan Sidwell on tracepoints , though I have not had the chance to look at what changes were being done. Another option is to script this up using gdb scripts / breakpoints and commands on hitting the breakpoints, but I guess you know that already. cheers Ramana > > thanks > jim > >
> > > >> From: Ramana Radhakrishnan >> To: james osburn >> CC: gdb@sources.redhat.com >> Subject: Re: what are gdbstubs? >> Date: Fri, 25 Mar 2005 04:44:56 +0530 >> >> james osburn wrote: >> >>> a m using uclibc on the 386 platform i am more interested >>> in tracing than setting break points. >> >> >> What do you exactly mean by tracing ? Function calls or get some other >> trace information ? >> >> >>> i want a way to remotely >>> what my program execute but i dont have a large budget >>> (hence the gnu tools) >>> any ideas on that? >>> jim >>> >>>
>>> >>> >>> >>>> From: Ramana Radhakrishnan >>>> To: james osburn >>>> CC: gdb@sources.redhat.com >>>> Subject: Re: what are gdbstubs? >>>> Date: Fri, 25 Mar 2005 04:37:19 +0530 >>>> >>>> Hi , >>>> >>>>> I have been reading the gdb docs and as i interpret them >>>>> i need to link the gdb stub file with my excecuteable >>>>> to do remote debugging. is this correct? >>>> >>>> >>>> >>>> Yes you do. >>>> >>>>> do you have any experience with this? >>>> >>>> >>>> >>>> I have not used *-stub.c for any debugging in a while now. I must >>>> say however that if you were using linux / uClinux on your embedded >>>> system , you could choose to use gdbserver instead in which case the >>>> linking is not required. >>>> >>>> cheers >>>> Ramana >>>> >>>> >>>> -- >>>> Ramana Radhakrishnan >>>> GNU Tools >>>> codito ergo sum (www.codito.com) >>>> >>> >> >> >> -- >> Ramana Radhakrishnan >> GNU Tools >> codito ergo sum (www.codito.com) >> > -- Ramana Radhakrishnan GNU Tools codito ergo sum (www.codito.com)