Py_AddPendingCall instead of messing with the GIL.

ionelmc · Sep 3, 2017 · d9cd6ef · d9cd6ef
1 parent 601ea48
commit d9cd6ef
Showing 1 changed file with 2 additions and 6 deletions.
diff --git a/src/hunter/remote.py b/src/hunter/remote.py
@@ -70,15 +70,11 @@ def gdb_bootstrap(args, activation_payload, deactivation_payload):
     print('WARNING: Using GDB may deadlock the process or create unpredictable results!')
     activation_command = [
         'gdb', '-p', str(args.pid), '-batch',
-        '-ex', 'call PyGILState_Ensure()',
-        '-ex', 'call PyRun_SimpleString(%s)' % json.dumps(activation_payload),
-        '-ex', 'call PyGILState_Release($1)',
+        '-ex', 'call Py_AddPendingCall(PyRun_SimpleString, %s)' % json.dumps(activation_payload),
     ]
     deactivation_command = [
         'gdb', '-p', str(args.pid), '-batch',
-        '-ex', 'call PyGILState_Ensure()',
-        '-ex', 'call PyRun_SimpleString(%s)' % json.dumps(deactivation_payload),
-        '-ex', 'call PyGILState_Release($1)',
+        '-ex', 'call Py_AddPendingCall(PyRun_SimpleString, %s)' % json.dumps(deactivation_payload),
     ]
     check_call(activation_command)
     try: