- This topic has 6 replies, 4 voices, and was last updated 10 years, 11 months ago by
.
-
Posts
-
1, start in linux: valgrind –vgdb-error=0 aa.bin
2, custom Project properties -> GDB settings -> customize GDB startup commands to (target remote | /usr/lib/valgrind/../../bin/vgdb)vs can stopped in program entry, but with no symbols, after use file aa.bin, symbols works in gdb, but vs still don’t show source code etc.
any way to do it now?Does this still work with VisualGDB 3.1? It is telling me
The “remote” target does not support “run”. Try “help target” or “continue”.
I assume VisualGDB uses the “run” command and it would only work with “continue”? I tried adding “continue”, but now Visual Studio / VisualGDB is hanging on “The following GDB command is taking too long to complete -break-list”
Shouldn’t this work? It’s telling me “Program isn’t being run”. http://i.imgur.com/yherlih.png
I made a new project with that same configuration as I’m pretty sure that this should work and now it’s showing this error: http://i.imgur.com/EZ5rdyH.png
and when I click on “show log”, it just says “Your VisualGDB trial expires in 30 days!”….
Yes, here it is:
https://dl.dropboxusercontent.com/u/700060/LinuxProject3-Debug.vgdbsettings
Maybe it’s just a problem with the trial version? It’s weird that the log only says “Your VisualGDB trial expires in 27 days!”
Hi,
We have investigated your problem and found a bug in VisualGDB. When running the gdbserver command VisualGDB always tries to use the deployment machine which is not set in your case.
We will fix this in the next release. As a workaround please enable the “Deploy executable on a different machine” checkbox in the VisualGDB Project Properties and specify the same machine as the deployment machine.If you get ‘broken pipe’ messages please ensure that no other valgrind instances are running in the background.
- You must be logged in to reply to this topic.