|
From: <sv...@va...> - 2015-03-22 11:02:06
|
Author: tom
Date: Sun Mar 22 11:01:58 2015
New Revision: 15033
Log:
Include the platform name in the unhandled system call message
We often get bug reports for an unhandled system call which don't
make it clear what platform is in use, which makes it impossible
to know which system call it is.
Modified:
trunk/coregrind/m_syswrap/syswrap-main.c
trunk/memcheck/tests/x86-linux/scalar.stderr.exp
Modified: trunk/coregrind/m_syswrap/syswrap-main.c
==============================================================================
--- trunk/coregrind/m_syswrap/syswrap-main.c (original)
+++ trunk/coregrind/m_syswrap/syswrap-main.c Sun Mar 22 11:01:58 2015
@@ -1291,8 +1291,8 @@
/*OUT*/SyscallStatus* status,
/*OUT*/UWord* flags )
{
- VG_(dmsg)("WARNING: unhandled syscall: %s\n",
- VG_SYSNUM_STRING(args->sysno));
+ VG_(dmsg)("WARNING: unhandled %s syscall: %s\n",
+ VG_PLATFORM, VG_SYSNUM_STRING(args->sysno));
if (VG_(clo_verbosity) > 1) {
VG_(get_and_pp_StackTrace)(tid, VG_(clo_backtrace_size));
}
Modified: trunk/memcheck/tests/x86-linux/scalar.stderr.exp
==============================================================================
--- trunk/memcheck/tests/x86-linux/scalar.stderr.exp (original)
+++ trunk/memcheck/tests/x86-linux/scalar.stderr.exp Sun Mar 22 11:01:58 2015
@@ -4070,7 +4070,7 @@
-----------------------------------------------------
9999: 9999 1e
-----------------------------------------------------
-WARNING: unhandled syscall: 9999
+WARNING: unhandled x86-linux syscall: 9999
You may be able to write your own handler.
Read the file README_MISSING_SYSCALL_OR_IOCTL.
Nevertheless we consider this a bug. Please report
|