From: Mark Wielaard <mjw@redhat.com>
To: systemtap@sourceware.org
Subject: Re: Enabling dwarf unwinder for ppc64
Date: Fri, 21 Oct 2011 15:02:00 -0000 [thread overview]
Message-ID: <1319209354.1087.31.camel@springer.wildebeest.org> (raw)
In-Reply-To: <1319205269.1087.26.camel@springer.wildebeest.org>
On Fri, 2011-10-21 at 15:54 +0200, Mark Wielaard wrote:
> On Fri, 2011-10-21 at 15:34 +0200, Mark Wielaard wrote:
> > Host: Linux ibm-ps701-01-lp2.rhts.eng.bos.redhat.com
> > 2.6.32-209.el6.ppc64 #1 SMP Wed Oct 12 03:52:18 EDT 2011 ppc64 ppc64
> > ppc64 GNU/Linux
> > Snapshot: version 1.7/0.152 commit release-1.6-340-gb100897
> > GCC: 4.4.6 [gcc (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3)]
> > Distro: Red Hat Enterprise Linux Server release 6.2 Beta (Santiago)
> >
> > # of expected passes 2893
> > # of unexpected failures 127
> > # of unexpected successes 9
> > # of expected failures 255
> > # of untested testcases 65
> > # of unsupported tests 6
> >
> > About 100 of the unexpected failures are in the systemtap.unprivileged
> > testsuite, which I haven't investigated yet.
>
> While investigating, I found the following in
> testsuite/systemtap.unprivileged/unprivileged_myproc.exp
>
> # ppc64 needs a more restrictive constraint for the probe args
> if {[regexp "^(x86_64|i.86)$" $::tcl_platform(machine)] == 0} {
> set exeflags "$exeflags additional_flags=-DSTAP_SDT_ARG_CONSTRAINT=nr"
> }
>
> But (removing) that doesn't seem to change any of the results it seems.
> What is that used for?
I still haven't figured out what that is for, so I just left it in for
now. The actual issue was more mundane. On powerpc function symbols
start with a '.', so the address extraction in those testcases failed.
Fixed as follows:
commit 50c8dc801a8fd22a3f6b8fd00e5d29944dfffbab
Author: Mark Wielaard <mjw@redhat.com>
Date: Fri Oct 21 16:49:02 2011 +0200
Extract addr_of for unprivileged_[my]probes.exp once and with
optional dot.
Some architectures prefix function symbols with a '.', so accept an
optional dot prefix. Also extract each symbol only once instead of
for each pass over the list.
With that both x86_64 and ppc64 give the same number of failures for the
systemtap.unprivileged testsuites:
Running /home/mark/src/systemtap/testsuite/systemtap.unprivileged/unprivileged_embedded_C.exp ...
Running /home/mark/src/systemtap/testsuite/systemtap.unprivileged/unprivileged_myproc.exp ...
FAIL: unprivileged myproc: not tested: process(string).library(string).plt
FAIL: unprivileged myproc: not tested: process(string).library(string).plt.statement(number)
FAIL: unprivileged myproc: not tested: process(string).library(string).plt(string)
FAIL: unprivileged myproc: not tested: process(string).library(string).plt(string).statement(number)
FAIL: unprivileged myproc: not tested: process(string).plt
FAIL: unprivileged myproc: not tested: process(string).plt.statement(number)
FAIL: unprivileged myproc: not tested: process(string).plt(string)
FAIL: unprivileged myproc: not tested: process(string).plt(string).statement(number)
Running /home/mark/src/systemtap/testsuite/systemtap.unprivileged/unprivileged_probes.exp ...
FAIL: unprivileged probes: not tested: process(string).library(string).plt
FAIL: unprivileged probes: not tested: process(string).library(string).plt.statement(number)
FAIL: unprivileged probes: not tested: process(string).library(string).plt(string)
FAIL: unprivileged probes: not tested: process(string).library(string).plt(string).statement(number)
FAIL: unprivileged probes: not tested: process(string).plt
FAIL: unprivileged probes: not tested: process(string).plt.statement(number)
FAIL: unprivileged probes: not tested: process(string).plt(string)
FAIL: unprivileged probes: not tested: process(string).plt(string).statement(number)
Cheers,
Mark
prev parent reply other threads:[~2011-10-21 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 11:22 Mark Wielaard
2011-10-13 22:21 ` Mark Wielaard
2011-10-20 14:37 ` Mark Wielaard
2011-10-20 18:51 ` Mark Wielaard
2011-10-21 13:35 ` Mark Wielaard
2011-10-21 13:54 ` Mark Wielaard
2011-10-21 15:02 ` Mark Wielaard [this message]
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=1319209354.1087.31.camel@springer.wildebeest.org \
--to=mjw@redhat.com \
--cc=systemtap@sourceware.org \
/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).