From: David Wilder <dwilder@us.ibm.com>
To: David Smith <dsmith@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Results of systemtap-20071124 snapshot on s390x
Date: Thu, 06 Dec 2007 22:58:00 -0000 [thread overview]
Message-ID: <47587E7C.2040105@us.ibm.com> (raw)
In-Reply-To: <474EE031.800@redhat.com>
David Smith wrote:
> David Smith wrote:
>> David Wilder wrote:
>>
>> Interesting. The problem isn't that the marker the test used didn't
>> have an argument. Otherwise, you would have gotten an error that looked
>> like the error message you got above (that comes from K_MARKER05). For
>> instance, here's what I get when I try to compile a probe that uses
>> '$arg1' when a marker doesn't have any arguments.
>>
>> # stap -e 'probe kernel.mark("mm_handle_fault_exit") { print($arg1)}'
>> semantic error: invalid marker argument number: identifier '$arg1'
>> at <input>:1:51 while resolving probe point
>> kernel.mark("mm_handle_fault_exit")
>> Pass 2: analysis failed. Try again with more '-v' (verbose) options.
>>
>> What's weird is that only K_MARKER04 is failing. K_MARKER01 and
>> K_MARKER02 compile correctly, yet K_MARKER04 doesn't compile. The only
>> difference between K_MARKER02 and K_MARKER04 is that K_MARKER04 prints
>> $arg1.
>
> I may have just found and fixed this. In updating the marker test, I
> started receiving a similar failure (on x86). After debugging this a
> bit, I found that it was because the marker had more than one string
> argument - the translator was emitting invalid code in this case. I've
> fixed this now.
>
Thanks David, the Marker test is passing on s390 after your last change
and after installing the following patches to the 2.6.24-rc3 kernel:
linux-kernel-markers-create-modpost-file.patch
markers-support-multiple-probes.patch
prev parent reply other threads:[~2007-12-06 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 0:34 David Wilder
2007-11-27 14:36 ` David Smith
2007-11-27 22:05 ` David Wilder
2007-11-27 22:34 ` David Smith
2007-11-27 23:07 ` David Wilder
2007-11-28 15:08 ` David Smith
2007-11-28 18:18 ` Frank Ch. Eigler
2007-11-29 15:52 ` David Smith
2007-12-06 22:58 ` David Wilder [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=47587E7C.2040105@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=dsmith@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).