From: Daniel Jacobowitz <drow@false.org>
To: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
Cc: james osburn <jjosburn@hotmail.com>, gdb@sources.redhat.com
Subject: Re: tracing ( was Re: what are gdbstubs?)
Date: Thu, 24 Mar 2005 23:47:00 -0000 [thread overview]
Message-ID: <20050324234815.GA14274@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2005-03-24 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 16:58 what are gdbstubs? james osburn
2005-03-24 17:08 ` Ramana Radhakrishnan
2005-03-24 22:55 ` james osburn
2005-03-24 23:08 ` Ramana Radhakrishnan
2005-03-24 23:12 ` james osburn
2005-03-24 23:15 ` Ramana Radhakrishnan
2005-03-24 23:25 ` tracing ( was Re: what are gdbstubs?) james osburn
2005-03-24 23:44 ` Ramana Radhakrishnan
2005-03-24 23:47 ` Daniel Jacobowitz [this message]
2005-03-24 23:48 ` james osburn
2005-03-24 23:59 ` Ramana Radhakrishnan
2005-03-25 0:09 ` Ramana Radhakrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050324234815.GA14274@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jjosburn@hotmail.com \
--cc=ramana.radhakrishnan@codito.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox