- This topic has 2 replies, 2 voices, and was last updated 9 years, 4 months ago by
.
-
Posts
-
Running VisualGDB 4.3 (also tried beta) and Visual Studio 2013.
Up until a couple days ago, I could debug everything and anything in Visual Studio, but now when I go to debug, I’m getting a these “GDB Command Timeout” errors.
Once in a great while (1 or 20 tries) I can get everything to work just fine). I really have no idea as to what is happening here. I have uninstalled, reinstalled, rebooted, blown away Visual Studio (which allowed it work more than the 1 of 20 for a little while), ???
Let me know if you need any more settings or what not from me. Have wasted 2 days of time with this one so far.
More info from VisualGDB output : “../../gdb/cp-namespace.c:825: internal-error: cp_lookup_nested_symbol…” “A problem internal to gDB has been detected.”
The problem seems to go away when I add a breakpoint to my main.cpp. main.cpp is fairly inconsequential within my program (just calls out to another service/function), but must cause VisualGDB to do something “different”.
This looks like a gdb bug. Please update your gdb to a newer version. If you are using a Linux one, you can build a new one from sources by downloading the sources, unpacking them and running “./configure && make” in the source directory. Then specify the built gdb binary in VisualGDB Project Properties and VisualGDB will use it to debug your projects.
- You must be logged in to reply to this topic.