From c0468bd4c289b9392e7867f2eb1b9bbc6e9cf196 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Thu, 27 Jun 2013 20:01:53 -0700 Subject: [PATCH] Use explicit sys_utimes functions for at_var.exp This test wants to access a typed $utimes variable, but on architectures with HAVE_SYSCALL_WRAPPERS the main sys_utimes has all long arguments. And starting in 3.10, all archs have syscall wrappers, yay! For this test's purposes, it's perfectly fine to use the inline SYSC_utimes where that exists. --- testsuite/systemtap.base/at_var.stp | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/testsuite/systemtap.base/at_var.stp b/testsuite/systemtap.base/at_var.stp index 86f19bb93..9fb4d2187 100644 --- a/testsuite/systemtap.base/at_var.stp +++ b/testsuite/systemtap.base/at_var.stp @@ -13,7 +13,10 @@ probe process.function("sub") printf("@var(\"foo\")->bar: %d\n", @var("foo")->bar); } -probe syscall.utimes +/* NB: can't just use syscall.utimes, because with HAVE_SYSCALL_WRAPPERS the + * primary sys_utimes function has all long types. Also, all architectures + * effectively HAVE_SYSCALL_WRAPPERS starting in 3.10! */ +probe kernel.function("SYSC_utimes")!, kernel.function("sys_utimes") { printf("$utimes$$: %s\n", $utimes$$); printf("$utimes[1]$$: %s\n", $utimes[1]$$); -- 2.43.5