[Gd-chatter] r11555 - trunk/fundev/sources/runtime-manager/debugger-nub/x86-win32

[andreas at gwydiondylan.org]

Author: andreas
Date: Tue Dec 18 00:17:00 2007
New Revision: 11555

Modified:
   trunk/fundev/sources/runtime-manager/debugger-nub/x86-win32/remote_function_call.c
Log:
bug: 6503

Fix the dreaded "Failed to allocate stack in Spy call" problem
by increasing the timeout from 1s to 30s.  Loading large applications
for debugging might just take that long.


Modified: trunk/fundev/sources/runtime-manager/debugger-nub/x86-win32/remote_function_call.c
==============================================================================
--- trunk/fundev/sources/runtime-manager/debugger-nub/x86-win32/remote_function_call.c	(original)
+++ trunk/fundev/sources/runtime-manager/debugger-nub/x86-win32/remote_function_call.c	Tue Dec 18 00:17:00 2007
@@ -223,7 +223,7 @@
   execute_thread(thread);
 
   wait_for_stop_reason_internal
-     (process, TRUE, 1000, &code, STOP_REASON_WAIT_SPY);
+     (process, TRUE, 30000, &code, STOP_REASON_WAIT_SPY);
 
   if (code == SPY_RETURN_DBG_EVENT) {
     // Resume the suspended threads.
@@ -260,9 +260,9 @@
             sizeof(ALLOCATOR_INSTRUCTION_SEQUENCE),
             &bytes_written);
     SetThreadContext(thread->ThreadHandle, &context_as_was);
-    nub_debug_message("Error: Micro Spy call failed on Thread %=",
+    nub_debug_message("Error: Micro Spy call failed on Thread %=, code: %=",
 		      (TARGET_ADDRESS)thread->ThreadHandle,
-		      (TARGET_ADDRESS)NULL);
+		      (TARGET_ADDRESS)code);
     return (NULL);
   }
   // Resume the suspended threads.