Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Benjamin Tze-Kit Lee <btlee@sfu.ca>, gdb@sources.redhat.com
Subject: Re: using tracepoints function with both host and target on same computer
Date: Wed, 07 Aug 2002 06:11:00 -0000	[thread overview]
Message-ID: <20020807131141.GA31656@nevyn.them.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020807080720.16955E-100000@is>

On Wed, Aug 07, 2002 at 08:08:54AM +0300, Eli Zaretskii wrote:
> 
> On Tue, 6 Aug 2002, Daniel Jacobowitz wrote:
> 
> > If I have more free time than I expect to (:-) then I would like
> > to add this to gdbserver; but that won't be for at least six months.
> 
> IMHO, tracepoints should really become part of GDB itself, even for 
> native debugging.  That would allow us to debug programs where timing is 
> critical, such as real-time software, Emacs display engine, etc.  I miss 
> that feature a lot.

I agree; but my dream is to get back to modularization so that
gdbserver will use a small library that GDB also uses to do the actual
tracing, and tracepoints can be there.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-08-07 13:11 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 [this message]
2002-08-07  7:51     ` William A. Gatliff
2002-08-07  8:01       ` Daniel Jacobowitz
2002-08-07  8:21         ` William A. Gatliff
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=20020807131141.GA31656@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=btlee@sfu.ca \
    --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