|
From: <sv...@va...> - 2012-08-18 09:50:40
|
philippe 2012-08-18 10:50:27 +0100 (Sat, 18 Aug 2012)
New Revision: 12879
Log:
Fix 301281 valgrind hangs on OS X when the process calls system()
This should fix the bug (but could not test it : no MacOSX).
See equivalent code in syswrap-generic.c and comment
in pub_tool_gdbserver.h:
// tid == 0 indicates to stop gdbserver and report to gdb
// that the valgrind-ified process has exited.
Modified files:
trunk/coregrind/m_syswrap/syswrap-darwin.c
Modified: trunk/coregrind/m_syswrap/syswrap-darwin.c (+1 -1)
===================================================================
--- trunk/coregrind/m_syswrap/syswrap-darwin.c 2012-08-18 07:45:07 +01:00 (rev 12878)
+++ trunk/coregrind/m_syswrap/syswrap-darwin.c 2012-08-18 10:50:27 +01:00 (rev 12879)
@@ -2840,7 +2840,7 @@
// to cleanup the gdbserver resources (e.g. the FIFO files).
// If child will be traced, we also terminate gdbserver: the new
// Valgrind will start a fresh gdbserver after exec.
- VG_(gdbserver) (tid);
+ VG_(gdbserver) (0);
}
// Set up the child's exe path.
|