[andu]

I believe it was a buggy device.
I also tried your previous suggestions and worked.
Thanks!

[andu]

I did not try your previous suggestion, because I created the visual GDB project from the scratch(several times) and every time I try to debug I receive the following error:”Cannot connect to gdbserver. Please start debugging again, If the problem persist, increase additional gdbserver startup delay in VisualGDB project settings”.
And then I don’t receive any suggestion from VisualGDB ->”The knowledge base contains no information about your problem. Please ensure that you have the latest NDK/SDK installed and then try debugging again.”
And sometimes(rarely) I receive same error message but none of the fixes from http://visualgdb.com/KB/?ProblemID=nopkg work.

My steps are: stat debug session from Eclipse then attach to the running activity from Visual Studio. An window with “VisualGDB is starting the Android debug session..” appears and then the previous error message.

Gdbserver log:
Attached; pid = 5599
Listening on port 5039
Remote debugging from host 127.0.0.1

GDB log:
-gdb-set solib-search-path C:/Users/andumitru/AppData/Local/VisualGDB/AndroidBinaryCache/0123456789ABCDEF;D:/…/ADCTest/obj/local/armeabi
^done
-target-select remote :5039
~”Ignoring packet error, continuing…n”
~”Ignoring packet error, continuing…n”
=thread-group-started,id=”i1″,pid=”42000″
=thread-created,id=”1″,group-id=”i1″
~”Ignoring packet error, continuing…n”
=thread-group-exited,id=”i1″
^error,msg=”Malformed response to offset query, timeout”

I am using the latest SDK and Android NDK, Revision 8b version and Visual studio 2008. Do you have any idea how to fix this?
The odd thing is that yesterday worked and I did the same steps as today(but I erased that project), the only thing that is different is the device I’m running the application on. This can be an issue?

Thanks

[Author]

Posts