From: Eugeniy Meshcheryakov <eugeniy.meshcheryakov@googlemail.com>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
Systemtap <systemtap@sources.redhat.com>
Subject: Re: Stap is translating to functions in __exit sections...and later module load fails
Date: Fri, 13 Oct 2006 21:29:00 -0000 [thread overview]
Message-ID: <20061013212914.GA14915@localhost.localdomain> (raw)
In-Reply-To: <C56DB814FAA30B418C75310AC4BB279DC4C745@scsmsx413.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
13 жовтня 2006 о 14:02 -0700 Stone, Joshua I написав(-ла):
> The translator blacklist tries to avoid such functions by checking the
> section name -- anything within a section beginning with '.exit.' (e.g.,
> .exit.text) is blacklisted, and thus won't match a function("*").
>
> Does IA64 do something different with the __exit sections?
It is strange that translator sees it at all. The code is
static void __exit
exit_pfm_fs(void)
{
unregister_filesystem(&pfm_fs_type);
mntput(pfmfs_mnt);
}
and this function is never used...
--
Eugeniy Meshcheryakov
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-13 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 21:02 Stone, Joshua I
2006-10-13 21:10 ` Keshavamurthy Anil S
2006-10-13 21:29 ` Eugeniy Meshcheryakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 1:06 Stone, Joshua I
2006-10-18 22:15 ` Keshavamurthy Anil S
2006-10-18 0:52 Keshavamurthy, Anil S
2006-10-13 22:28 Stone, Joshua I
2006-10-13 22:37 ` Keshavamurthy Anil S
2006-10-13 23:07 ` Eugeniy Meshcheryakov
2006-10-16 11:27 ` bibo,mao
2006-10-13 21:26 Stone, Joshua I
2006-10-13 21:56 ` Keshavamurthy Anil S
2006-10-13 20:26 Keshavamurthy, Anil S
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=20061013212914.GA14915@localhost.localdomain \
--to=eugeniy.meshcheryakov@googlemail.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=joshua.i.stone@intel.com \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).