From: "Chris January" <chris@atomice.net>
To: <gdb@sources.redhat.com>
Subject: RE: GDB as a program analyzer - some thoughts
Date: Tue, 18 May 2004 17:04:00 -0000 [thread overview]
Message-ID: <ICEBIHGCEJIPLNMBNCMKAELJGAAA.chris@atomice.net> (raw)
In-Reply-To: <40AA23FD.6040103@lifl.fr>
> This post deals about using GDB for non-debugging purposes, I hope it's
> not offtopic. I'm also hoping to find some people interested in the same
> matters than I to discuss about how GDB could be improved for analysis
> purposes.
See:
http://www.argreenhouse.com/papers/hira/spe93.pdf
for a program trace/dynamic analysis tool built on top of gdb and gcc.
I'm currently working on a program tracing tool for i386 that uses Valgrind
and GDB for my final year project. It should allow you to query program
traces using SQL.
Example:
set filter {x>5}
history
or some similar syntax.
would show you all the places when (and where) the variable x (when in
scope) had a value greater than 5.
Feel free to mail me off list if you want to discuss this kind of thing any
further.
Regards,
Chris
next prev parent reply other threads:[~2004-05-18 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 14:57 Alexandre Courbot
2004-05-18 15:49 ` Ramana Radhakrishnan
2004-05-18 17:04 ` Chris January [this message]
2004-05-20 3:11 ` 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=ICEBIHGCEJIPLNMBNCMKAELJGAAA.chris@atomice.net \
--to=chris@atomice.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