From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23664 invoked by alias); 2 Dec 2011 16:15:40 -0000 Received: (qmail 23642 invoked by uid 22791); 2 Dec 2011 16:15:39 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Dec 2011 16:15:23 +0000 From: "mjw at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/13467] New: user array indexing pointer_array.exp testcase fails on s390x needs @user($ptr) Date: Fri, 02 Dec 2011 19:36:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjw at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00285.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13467 Bug #: 13467 Summary: user array indexing pointer_array.exp testcase fails on s390x needs @user($ptr) Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: runtime AssignedTo: systemtap@sourceware.org ReportedBy: mjw@redhat.com Classification: Unclassified pointer_array.stp basically does: probe syscall.execve { println(user_string($argv[0])) } The $argv[0] is evaluated in kernel context, but is really a user pointer. So you will get a ERROR: kernel read fault at 0x00000000859fa100 (addr) near identifier '$argv'. The following would "fix" it: probe syscall.execve { println(user_string(user_long($argv))) } But the test really is about array indexing. The next tests try to extract the individual chars with $argv[0][1], etc. We could rewrite the testcase to use a user array in a user probe context. But maybe we need some kind of @user($ptr) construct, which would then give you an object that can be evaluated through []/-> as if in a user probe context? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.