RE: [patch 2/4] ia64 use trace hook | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
There is one warning from the compiler:
arch/ia64/kernel/ptrace.c:1243: warning: ignoring return value of 'tracehook_report_syscall_entry', declared with attribute warn_unused_result
Caused by this part of patch 2:
Index: linux/arch/ia64/kernel/ptrace.c
...
@@ -1260,9 +1239,8 @@ syscall_trace_enter (long arg0, long arg
long arg4, long arg5, long arg6, long arg7,
struct pt_regs regs)
...
+ if (test_thread_flag(TIF_SYSCALL_TRACE))
+ tracehook_report_syscall_entry(®s);
But apart from that it all seems OK.
How do I tell whether it is all working? Roland's wiki
that you pointed to in patch 0/4 doesn't have any testing
tips (and seems to have some old information ... it talks
about CONFIG_UTRACE being available after HAVE_ARCH_TRACEHOOK
is enabled ... but grep says there are no UTRACE references in
the kernel).
-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux MIPS Home] [Kernel List] [Sparc Linux] [DCCP] [Linux ARM List] [Linux] [Photo] [Yosemite News] [MIPS Architecture] [Linux SCSI] [Linux x86_64] [Linux Hams] [Site Home]
![]() |