Bug 4770 - syscall.compat_futimesat argument $utime should be $t
Summary: syscall.compat_futimesat argument $utime should be $t
Status: RESOLVED DUPLICATE of bug 4752
Alias: None
Product: systemtap
Classification: Unclassified
Component: tapsets (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-10 15:34 UTC by William Cohen
Modified: 2007-07-10 19:02 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
patch to correct the argument used (388 bytes, patch)
2007-07-10 15:35 UTC, William Cohen 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Cohen 2007-07-10 15:34:28 UTC 
When running the testsuite on the snapshot found that the translator fail on the
buildok/syscall.stp and the systemtap.systemcall tests.


$ ../install/bin/stap -p4 ../src/testsuite/systemtap.syscall/sys.stp 
semantic error: unable to find local 'utimes' near pc 0xffffffff802a1e48
(alternatives: dfd filename t tv): identifier '$utimes' at
/home/wcohen/stap_snap_200707091638/install/share/systemtap/tapset/syscalls.stp:945:29
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

Found that the argument in compat_sys_futimesat is "t" not "utime". Have a patch
that fixes the problem on the 2.6.22 and the RHEL4 kernels.
Comment 1 William Cohen 2007-07-10 15:35:18 UTC 
Created attachment 1914 [details]
patch to correct the argument used
Comment 2 Martin Hunt 2007-07-10 19:02:32 UTC 

*** This bug has been marked as a duplicate of 4752 ***