From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27555 invoked by alias); 24 Mar 2005 23:48:49 -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 27362 invoked from network); 24 Mar 2005 23:48:38 -0000 Received: from unknown (HELO hotmail.com) (64.4.31.40) by sourceware.org with SMTP; 24 Mar 2005 23:48:38 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Mar 2005 15:48:38 -0800 Message-ID: Received: from 208.54.95.129 by by13fd.bay13.hotmail.msn.com with HTTP; Thu, 24 Mar 2005 23:48:37 GMT X-Originating-Email: [jjosburn@hotmail.com] X-Sender: jjosburn@hotmail.com In-Reply-To: <424350D3.5080200@codito.com> From: "james osburn" To: gdb@sources.redhat.com Bcc: Subject: Re: tracing ( was Re: what are gdbstubs?) Date: Thu, 24 Mar 2005 23:48:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 24 Mar 2005 23:48:38.0071 (UTC) FILETIME=[FFF5A470:01C530CB] X-SW-Source: 2005-03/txt/msg00230.txt.bz2 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
>From: Ramana Radhakrishnan >To: james osburn >CC: gdb@sources.redhat.com >Subject: Re: tracing ( was Re: what are gdbstubs?) >Date: Fri, 25 Mar 2005 05:14:19 +0530 > > >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) >