[Bug tapsets/6969] syscall tapset broken on s390x

[mjw at redhat dot com]

------- Additional Comments From mjw at redhat dot com  2008-10-23 07:35 -------
David tracked it down to my commit:

commit e483d9dfa614ee17b488df7224ee22a0f7dc9386
Author: Mark Wielaard <mwielaard@redhat.com>
Date:   Wed May 21 16:12:17 2008 +0200

    Use pointer_arg to fetch arguments for syscall.utime and compat_utime.

diff --git a/tapset/ChangeLog b/tapset/ChangeLog
index a0f14de..2c4ba4d 100644
--- a/tapset/ChangeLog
+++ b/tapset/ChangeLog
@@ -1,3 +1,8 @@
+2008-05-21  Mark Wielaard  <mwielaard@redhat.com>
+
+       * syscalls2.stp (syscall.utime): Use pointer_arg to fetch arguments.
+       (syscall.compat_utime): Likewise.

This was done to fix this issue:
http://sourceware.org/ml/systemtap/2008-q2/msg00397.html

FAIL: semok/nodwf02.stp
FAIL: semok/nodwf05.stp

So I changed these utime calls to also work with dwarfless probes:
http://sourceware.org/ml/systemtap/2008-q2/msg00399.html

A bit more analysis is in:
http://sourceware.org/ml/systemtap/2008-q2/msg00410.html

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6969

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.