From: Benjamin Tze-Kit Lee <btlee@sfu.ca>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: doing tracepoint on remote target through gdbserver
Date: Thu, 08 Aug 2002 12:25:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0208081217280.22074-100000@fraser.sfu.ca> (raw)
In-Reply-To: <20020808191414.GA23293@nevyn.them.org>
Hi,
Sorry, but just want to make things clear.
Does that mean that the gdb feature "tracepoint" does not actually works?
Coz in order to do tracepoint, we must do that through remote
debugging. And to do remote debugging, one can only use gdbserver or
through some sort of serial ports. However, gdbserver does not support
tracepoint and there are no stub avalible that can do this.
So is there a way that I can test out on the tracepoint function?
Thank you very much.
Benjamin Lee
On Thu, 8 Aug 2002, Daniel Jacobowitz wrote:
> On Thu, Aug 08, 2002 at 12:08:56PM -0700, Benjamin Tze-Kit Lee wrote:
> > Hi all,
> >
> > I am trying to do tracepoint on a program through remote target debugging.
> > Everything seems to work as I am able to do remote debugging using
> > breakpoints through gdb on the host and gdbserver on the target. But when
> > I try to do "tstart" on the program, it gives me the message "Target does
> > not support this command.". Is there a specific way to turn on the
> > tracepoint option when I compile gdbserver? Or what could be the problem?
>
> As we said earlier, gdbserver does not support tracepoints, nor do any
> of the other stubs included with GDB. I don't know of any that do at
> this time.
>
> --
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer
>
next prev parent reply other threads:[~2002-08-08 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 12:09 Benjamin Tze-Kit Lee
2002-08-08 12:13 ` Daniel Jacobowitz
2002-08-08 12:25 ` Benjamin Tze-Kit Lee [this message]
2002-08-08 12:28 ` Daniel Jacobowitz
2002-08-08 12:55 ` William A. Gatliff
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=Pine.GSO.4.44.0208081217280.22074-100000@fraser.sfu.ca \
--to=btlee@sfu.ca \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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