Valgrind-side changes to track vx1786 (which was: Support x86 $int

0x40 .. 0x43 instructions on Linux.  Apparently these generate a
segfault and then restart the instruction.)

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

diff --git a/coregrind/m_scheduler/scheduler.c b/coregrind/m_scheduler/scheduler.c
index c3f09d05c32043d5d89bcf5019738dc2ef195544..cc69fd398c7729ea486b514ba82f844d72578e26 100644 (file)
--- a/coregrind/m_scheduler/scheduler.c
+++ b/coregrind/m_scheduler/scheduler.c
@@ -1045,10 +1045,14 @@ VgSchedReturnCode VG_(scheduler) ( ThreadId tid )
          break;
       }
 
-      case VEX_TRC_JMP_TRAP:
+      case VEX_TRC_JMP_SIGTRAP:
          VG_(synth_sigtrap)(tid);
          break;
 
+      case VEX_TRC_JMP_SIGSEGV:
+         VG_(synth_fault)(tid);
+         break;
+
       case VEX_TRC_JMP_NODECODE:
    VG_(message)(Vg_UserMsg,
       "valgrind: Unrecognised instruction at address %p.", VG_(get_IP)(tid));