- This topic has 1 reply, 2 voices, and was last updated 9 years, 10 months ago by
.
-
Posts
-
I’m seeing frequent GDB command timeouts when debugging the SimpleGame project prior to hitting any breakpoint. It takes over a minute for me to regain access to Visual Studio. I’m seeing this same problem on two different computers and on both Visual Studio 2008 and 2013. All the tools were installed via the VisualGDB installer.
I’m using a Samsung Galaxy Tab2 connected via USB, NOT using the emulator, NOT using a virtual machine.
The first timeout is always -data-evaulate-expression “sizeof(void *)”, followed by several others.
They each stay open for >20 seconds, preventing me from accessing Visual Studio.
If I had the power to use just the breakpoints without peeking variables, I’d consider this product quite valuable. but as it is for me now, it’s unusable. I can break, then I have to stop debugging because these dialogs keep popping up.
I can’t imagine I’m the only one with this problem. Please help, Thanks!!
Hi,
First of all, you can increase the timeout before VisualGDB shows that box via Tools->Options->VisualGDB->Tweaking.
The timeout with “-data-evaulate-expression “sizeof(void *)”” is very strange, as this command does not involve communicating to the device, it should be handled locally based on the data from the ELF file. Hence, most likely the problem is in your GDB. You can diagnose it the following way:
* Try using a different version of GDB (selected on the Makefile Settings page)
* Try running the command manually via the GDB Session window. Does it always take that long or only during the first run?
* Select “all GDB interaction” in the GDB Session window and look for strange warnings. Does it take lots of time for GDB to load the initial symbols?
* Does your problem happen on smaller projects? If no, can you strip debugging symbols off some libraries you not currently stepping through? Does this improve performance?
- You must be logged in to reply to this topic.