From: "William A. Gatliff" <bgat@billgatliff.com>
To: "William A. Gatliff" <bgat@billgatliff.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
gdb@sources.redhat.com
Subject: Re: using tracepoints function with both host and target on same computer
Date: Wed, 07 Aug 2002 08:21:00 -0000 [thread overview]
Message-ID: <20020807102113.C5941@saturn.billgatliff.com> (raw)
In-Reply-To: <20020807150150.GA3872@nevyn.them.org>; from drow@mvista.com on Wed, Aug 07, 2002 at 11:01:50AM -0400
Daniel:
On Wed, Aug 07, 2002 at 11:01:50AM -0400, Daniel Jacobowitz wrote:
> You don't do them in actual realtime, but neither do you wait for all
> of GDB to process the event; you receive the breakpoint, collect
> tracepoint data, and immediately resume without touching GDB's event
> loop. It's a little slower than an in-application stub because it has
> to use ptrace to read memory/registers, but not substantially slower.
... except that I don't think you'd want to be doing that across a
9600bps remote link. Or, you'd at least want to have the option not
to.
> If you need better, you have to link a stub into the application. I
> think we've been investigating a library for that, but I don't know
> when/if it'll be available.
I'll take additions to gdbstubs. :^)
I've set out on several occasions to make time to add this feature,
but somehow I keep getting distracted by other fires. I'm now
available again, but I'm not currently in a position to do it gratis.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2002-08-07 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 13:34 Benjamin Tze-Kit Lee
2002-08-06 14:51 ` Daniel Jacobowitz
2002-08-06 22:11 ` Eli Zaretskii
2002-08-07 6:11 ` Daniel Jacobowitz
2002-08-07 7:51 ` William A. Gatliff
2002-08-07 8:01 ` Daniel Jacobowitz
2002-08-07 8:21 ` William A. Gatliff [this message]
2002-08-07 8:23 ` Daniel Jacobowitz
2002-08-07 8:24 ` 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=20020807102113.C5941@saturn.billgatliff.com \
--to=bgat@billgatliff.com \
--cc=eliz@is.elta.co.il \
--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