From: William Cohen <wcohen@redhat.com>
To: Martin Hunt <hunt@redhat.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: Summary of nightly tests 20060220
Date: Mon, 20 Feb 2006 20:05:00 -0000 [thread overview]
Message-ID: <43FA20F9.7020808@redhat.com> (raw)
In-Reply-To: <1140465215.3791.11.camel@monkey2>
Martin Hunt wrote:
>>FC5 i686 Linux 2.6.15-1.1948_FC5smp
>>
>>Stap translator summary of failed tests
>>buildok-seven.stp:
>> Unable to find identifier $type in function find_pid
>> Unable to find identifier $task in function detach_pid
>
>
> There don't appear to be significant changes in the sources to account
> for this. That makes it a likely gcc bug.
>
> Can someone write up the proper procedure to use to report these? I
> think it should be on the web page.
>
> Martin
>
>
The problem appears only in certain kernels. Possible causes for this
type of problem:
1) source code has changed so those variable/arguments don't exist
2) gcc tool chain not generating the proper debug information
3) stap is not finding them in the debugging information
Are there other possibilities or should this be finer grain resolution,
e.g. elfutils vs stap translator? The procedure should make it clear
which of the alternatives can be ruled out. Ideally, would like it to
point to to which one is causing the problem.
-Will
next prev parent reply other threads:[~2006-02-20 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 16:40 William Cohen
2006-02-20 19:52 ` Martin Hunt
2006-02-20 20:05 ` William Cohen [this message]
2006-02-20 20:36 ` Frank Ch. Eigler
2006-02-27 2:24 ` Suggestions for localizing problems with identifiers in SystemTap William Cohen
2006-02-27 4:40 ` Roland McGrath
2006-02-27 15:57 ` William Cohen
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=43FA20F9.7020808@redhat.com \
--to=wcohen@redhat.com \
--cc=hunt@redhat.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).