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.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15033

diff --git a/coregrind/m_syswrap/syswrap-main.c b/coregrind/m_syswrap/syswrap-main.c
index db534043d21f9c2b44e0efb2a505a710cc71ee91..04e52b6bba1526b8b5bbf0619700c50cfc5215df 100644 (file)
--- a/coregrind/m_syswrap/syswrap-main.c
+++ b/coregrind/m_syswrap/syswrap-main.c
@@ -1291,8 +1291,8 @@ void bad_before ( ThreadId              tid,
                   /*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));
    }

diff --git a/memcheck/tests/x86-linux/scalar.stderr.exp b/memcheck/tests/x86-linux/scalar.stderr.exp
index 9ed5406a927038784fbd2b30608b98d0d063bbfc..95b1e85774a10ac448018edde1c0d9869841f055 100644 (file)
--- a/memcheck/tests/x86-linux/scalar.stderr.exp
+++ b/memcheck/tests/x86-linux/scalar.stderr.exp
@@ -4070,7 +4070,7 @@ Syscall param process_vm_writev(rvec) points to unaddressable byte(s)
 -----------------------------------------------------
 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