It was erroneously asserted by Horst von Brand that 'linux-tracecalls'
"can not find where a function could be called through a pointer"
On the contrary, almost all the chains are terminated with a callback
function,
somewhat fewer with an init function, and fewest of all with a sy
e to the OOP-in-C style in the kernel) it has no chance.
Dear Doctor von Brand,
I believe the following should clear up your misunderstanding, perhaps due
to my poor original choice of words.
Carl Spalletta
PATCH #2
--- lnxtc-2.6.10.pl-2005-01-21 00:16:33.0 -0500
+++ lnxtc-2.6.10.
http://www.linuxrd.com/~carl/linux-tracecalls/KMALLOC.html#analysis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/l
--- Horst von Brand <[EMAIL PROTECTED]> wrote:
> If it can't find out where a function could be called through a pointer
> (very common due to the OOP-in-C style in the kernel) it has no chance.
Dear Horst,
No chance of what?
You do raise an interesting point. Linux-tracecalls already does
Only five minutes old, and already a patch ;)
--- lnxtc.pl-old 2005-01-19 12:09:00.0 -0800
+++ lnxtc.pl-new 2005-01-19 12:09:38.0 -0800
@@ -627,6 +627,7 @@
$debug = 0;
}
+$ENV{'PATH'}='/bin:/usr/bin';
#Redirect standard error to logfile (fatals also to browser)
>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,
'ln
On Monday July 25, 2001 Jasmin Brown wrote:
>Aufgaben:
>permanente Anpassung wichtiger Systemkomponenten an
unsere
et cetera
Since nobody jumped on the improbably named Yasmin
Brown & Jill Simmons for daring to post a classified
within these hallowed precincts, I submit herewith my
own contribu
7 matches
Mail list logo
