From: Carl Spalletta <cspalletta@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>
Subject: Linux-tracecalls, a clarification
Date: Fri, 21 Jan 2005 12:44:22 -0800 (PST) [thread overview]
Message-ID: <20050121204422.85137.qmail@web53808.mail.yahoo.com> (raw)
In-Reply-To: <200501192037.j0JKbpuA008501@laptop11.inf.utfsm.cl>
http://www.linuxrd.com/~carl/cgi-bin/lnxtc.pl?help
--- Horst von Brand <vonbrand@inf.utfsm.cl> wrote:
> Re: [ANNOUNCE] Linux-tracecalls, a new tool for Kernel development, released
>
> 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 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.000000000 -0500
+++ lnxtc-2.6.10.pl 2005-01-21 00:50:11.000000000 -0500
@@ -517,10 +517,22 @@
$leaf_node = 0;
$debug and print STDERR "\ncscope line is $full_caller_cscope";
- #Target is a callback
+ #TARGET IS A PSEUDO-CALLBACK, AN ARTIFACT OF CSCOPE:
+ #
+ #The name of an operations structure member, wrongly interpreted by
+ #cscope as the name of an actual function - it should be ignored,
+ #since it has been confused by cscope with the name of some actual
+ #caller. HOWEVER the callbacks are found anyway, under their actual names.
+ #and if any function pointed to by a callback is part of a chain to
+ #our initial target it _will_ be found, the same as any other caller.
+ #
if($full_caller_cscope =~ /\w+\s*->\s*${target_filefunc}\s*\(/)
{
- $debug and print STDERR "callback $target_filefunc ignored.\n";
+ $debug and
+ print STDERR "pseudo-callback $target_filefunc ignored.\n";
next;
}
next prev parent reply other threads:[~2005-01-21 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 19:38 [ANNOUNCE] Linux-tracecalls, a new tool for Kernel development, released Carl Spalletta
2005-01-19 20:37 ` Horst von Brand
2005-01-20 16:51 ` Carl Spalletta
2005-01-21 20:44 ` Carl Spalletta [this message]
2005-02-07 1:20 ` Linux-tracecalls, a clarification Werner Almesberger
2005-05-03 22:12 Carl Spalletta
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=20050121204422.85137.qmail@web53808.mail.yahoo.com \
--to=cspalletta@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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).