public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: maxim@mox.ru
Cc: gdb@sourceware.org
Subject: Re: tracepoints
Date: Mon, 23 Jan 2006 19:37:00 -0000	[thread overview]
Message-ID: <8f2776cb0601231134j6af5a41fl86743a120883d307@mail.gmail.com> (raw)
In-Reply-To: <6097c490601230332y7c07997ayf469667222e187d2@mail.gmail.com>

I don't know of any publicly available stub-side implementations,
either.  I'm working on adding support for tracepoints to KGDB, the
Linux kernel stub.  When I have something ready to share I'll let the
list know.

  parent reply	other threads:[~2006-01-23 19:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 13:49 tracepoints Maxim Osipov
2006-01-23 15:00 ` tracepoints Daniel Jacobowitz
2006-01-23 15:20   ` tracepoints Maxim Osipov
2006-01-23 19:37 ` Jim Blandy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-07 13:00 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-07 16:33 ` Tracepoints Jim Blandy
2003-10-08 17:21 ` Tracepoints Andrew Cagney
2003-10-06 13:39 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 21:03 ` Tracepoints Jim Blandy
2003-10-02 14:20 tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-02 13:16 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-02 19:23 ` Tracepoints Andrew Cagney
2001-07-11 10:38 Tracepoints Billalabeitia, Jose Carlos (IndSys, GEPM)
2001-03-21 15:59 tracepoints Edward Peschko
2001-03-21 15:59 ` tracepoints Eli Zaretskii
2001-03-21 15:59 tracepoints Nicolas.Thery
2001-03-21 15:59 ` tracepoints Eli Zaretskii
2001-03-21 15:59   ` tracepoints Eli Zaretskii
2001-03-21 15:59 ` tracepoints Edward Peschko
2001-03-21 15:59   ` tracepoints Eli Zaretskii
2001-02-27 19:50 tracepoints Edward Peschko

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=8f2776cb0601231134j6af5a41fl86743a120883d307@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb@sourceware.org \
    --cc=maxim@mox.ru \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).