This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: tracing ( was Re: what are gdbstubs?)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Ramana Radhakrishnan <ramana dot radhakrishnan at codito dot com>
- Cc: james osburn <jjosburn at hotmail dot com>, gdb at sources dot redhat dot com
- Date: Thu, 24 Mar 2005 18:48:15 -0500
- Subject: Re: tracing ( was Re: what are gdbstubs?)
- References: <BAY13-F3603224501BC18982C8A32D8400@phx.gbl> <424350D3.5080200@codito.com>
On Fri, Mar 25, 2005 at 05:14:19AM +0530, Ramana Radhakrishnan wrote:
>
> 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.
No - this isn't at all like tracepoints. You could implement this
using a decent frontend and MI, but it would be some work.
--
Daniel Jacobowitz
CodeSourcery, LLC