public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: Nicolas.Thery@Symbian.com
Cc: edwardp@excitehome.net, gdb@sources.redhat.com
Subject: Re: tracepoints
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <200103101720.MAA02667@indy.delorie.com> (raw)
In-Reply-To: <OFAC898AEE.C34D195E-ON80256A0A.0043EE62@Symbian.com>

> From: Nicolas.Thery@Symbian.com
> Date: Fri, 9 Mar 2001 12:24:12 +0000
> 
> I've never used tracepoints on GDB and I suspect they are not the same as
> the dbx/trace feature you refer to.  But FWIW here is a pointer to some
> documentation:
> 
>      http://sources.redhat.com/gdb/talks/esc-west-1999/

Thanks a lot for this pointer!

To get tracepoints documented was on my TODO for a long time.
Unfortunately, I don't know anything about tracepoints, and the code
doesn't have enough helpful comments to allow even minimal docs to be
written.

I'm willing to convert these HTML documents into Texinfo, but I have
two issues with this:

  - Is the stuff in the above documents still valid, or were
    significant changes introduced into tracepoints since then?

  - The main document pointed to by the above URL clearly says it's a
    proprietary documentation that cannot be changed or even
    reproduced without an express _written_ consent of Cygnus.  This
    is a far cry from the GFDL, and it seems to prohibit any work done
    by anyone to produce a chapter for the GDB manual using this
    stuff.

Michael Snyder and/or Jim Blandy, could you please help resolve these
two issues?

  parent reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 15:59 tracepoints Nicolas.Thery
2001-03-21 15:59 ` tracepoints Edward Peschko
2001-03-21 15:59   ` tracepoints Eli Zaretskii
2001-03-21 15:59 ` Eli Zaretskii [this message]
2001-03-21 15:59   ` tracepoints Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
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 ` tracepoints Jim Blandy
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-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=200103101720.MAA02667@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=Nicolas.Thery@Symbian.com \
    --cc=edwardp@excitehome.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).