From: Carl Spalletta <cspalletta@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Linux-tracecalls, a new tool for Kernel development, released
Date: Wed, 19 Jan 2005 11:38:32 -0800 (PST) [thread overview]
Message-ID: <20050119193832.34975.qmail@web53803.mail.yahoo.com> (raw)
>From http://www.linuxrd.com/~carl/cgi-bin/lnxtc.pl?help
"'LINUX-TRACECALLS' finds all call chains leading to a given function in the Linux
kernel, to some arbitrary depth. It consists of two parts - a set of specially
prepared cscope databases for the kernel source tree, and a perl program, 'lnxtc.pl',
to do the call chain discovery based on the information in the cscope DBs."
"It works, in part, by expanding function-yielding macros and by mangling function names
with the name of the file containing the function's definition, prior to creating the
cscope files."
"It is believed to be highly accurate.."
next reply other threads:[~2005-01-19 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 19:38 Carl Spalletta [this message]
2005-01-19 20:37 ` [ANNOUNCE] Linux-tracecalls, a new tool for Kernel development, released Horst von Brand
2005-01-20 16:51 ` Carl Spalletta
2005-01-21 20:44 ` Linux-tracecalls, a clarification Carl Spalletta
2005-02-07 1:20 ` Werner Almesberger
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=20050119193832.34975.qmail@web53803.mail.yahoo.com \
--to=cspalletta@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).