From: Edward Peschko <edwardp@excitehome.net>
To: gdb@sourceware.cygnus.com
Subject: tracepoints
Date: Tue, 27 Feb 2001 19:50:00 -0000 [thread overview]
Message-ID: <20010227195009.A26697@excitehome.net> (raw)
hey,
I was wondering exactly how to use tracepoints - I'd like to be able to say
(gdb) trace
and then be able to see the exact steps that my program takes after I
hit 'run'. dbx has this capability; I don't see why gdb shouldn't.
I apologize if this is a FAQ or it has been asked and answered before,
but:
1) the answer to this question is not in the FAQ
2) the man page doesn't have an answer either.
3) a search of the list archives shows that it has been *asked*
several times, but hasn't been *answered*.
so how about it? has anybody used the facility before and is there a
good pointer to how it is used?
Ed
next reply other threads:[~2001-02-27 19:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 19:50 Edward Peschko [this message]
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-03-21 15:59 tracepoints Edward Peschko
2001-03-21 15:59 ` tracepoints Eli Zaretskii
2001-07-11 10:38 Tracepoints Billalabeitia, Jose Carlos (IndSys, GEPM)
2003-10-02 13:16 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-02 19:23 ` Tracepoints Andrew Cagney
2003-10-02 14:20 tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 13:39 Tracepoints Newman, Mark (N-Superior Technical Resource Inc)
2003-10-06 21:03 ` 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
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
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=20010227195009.A26697@excitehome.net \
--to=edwardp@excitehome.net \
--cc=gdb@sourceware.cygnus.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