From: fche@redhat.com (Frank Ch. Eigler)
To: systemtap@sources.redhat.com
Subject: Re: Summary of nightly tests 20060220
Date: Mon, 20 Feb 2006 20:36:00 -0000 [thread overview]
Message-ID: <y0mr75xepi9.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <1140465215.3791.11.camel@monkey2>
hunt wrote:
> > 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. [...]
Yes, possibly. We will likely have a RH compiler person working on an
ongoing basis to fix such problems.
I can't find a message I remember writing to the mailing list about
the change I committed to buildok/seven.stp on 2006-02-07. So to
recap: It adds the "-u" stap flag to force all $target variables to be
expanded. This, while valuable to some extent in exposing debuginfo
problems, was meant to be a stopgap measure. To be considered
complete, the system calls tapset should eventually come with a test
case that exercises all the auxiliary / embedded-C functions, at least
at the buildok level. (This is what src/HACKING suggests.) At that
point, I would remove "-u", and let unresolved $target variables pass
quietly.
- FChE
next prev parent reply other threads:[~2006-02-20 20:36 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
2006-02-20 20:36 ` Frank Ch. Eigler [this message]
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=y0mr75xepi9.fsf@ton.toronto.redhat.com \
--to=fche@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).