From: Alexandre Courbot <Alexandre.Courbot@lifl.fr>
To: gdb@sources.redhat.com
Subject: Using gdb as a trace agent
Date: Mon, 17 May 2004 13:00:00 -0000 [thread overview]
Message-ID: <40A8B71B.8030200@lifl.fr> (raw)
Hello everyone,
In my quest to get datas out of a program as non-intrusively as possible
(I'm trying to get graphes out of the memory manager of an embedded
operating system), I'm having a close and interested look at gdb
tracepoints. It looks like a great solution, but unfortunately:
- It only works on remote targets, dixit the manual,
- Anyway, no remote target supports them.
Traditional breakpoints with additional commands are just too intrusive
to me, unfortunately. Is there anything I missed on the tracepoints
front? Or would anyone know a tool that I could use in replacement to
gdb to do this? (i.e. getting the values of some variables at some
points of the program, without slaughtering the source code).
Thanks for any information,
Alex.
--
Alexandre Courbot - PhD student
RD2P/LIFL
http://www.lifl.fr/~courbot
next reply other threads:[~2004-05-17 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 13:00 Alexandre Courbot [this message]
2004-05-17 15:36 ` Jim Blandy
2004-05-17 16:49 ` Alexandre Courbot
2004-05-17 18:09 ` Eli Zaretskii
2004-05-17 18:29 ` Jim Blandy
2004-05-17 22:17 ` Alexandre Courbot
2004-05-18 7:07 ` Ramana Radhakrishnan
2004-05-18 8:33 ` Alexandre Courbot
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=40A8B71B.8030200@lifl.fr \
--to=alexandre.courbot@lifl.fr \
--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