[cpuser]

Ok, thanks, that would be extremely useful, especially since you support saving the debug APK parameters under a given name. That would make for a great experience.

In the meantime, a co-worker showed me that I can simply call the start the command with parameters with adb manually after the executable is already started under the debugger, and I am getting the proper code path executed in my code.

Thanks!

[cpuser]

Hi,

Yes, “Disable -file-list-exec-source-files” seems to fix the issue and doesn’t seem to have any bad consequence for me, I am still getting the symbols and it still opens the files in Visual Studio. The breakpoints seem to work fine.

Sorry I am totally new to Android and GDB, and I was just expecting a flowless Visual Studio-like experience 🙂
I am using a native windows 7, no VM.

By Ant I meant that we have a very complicated build process with our own makefiles for the native part and then ant to make the package, so I am just using the option to debug an APK I have built, I can’t really make a Visual Studio VisualGDB project.

Thanks for the quick answer!

[cpuser]

Quick update. I had another case where I was able to set a breakpoint and step.

I started the executable. One thread had an infinite loop in it.
I used attach to existing instance
I used debugger pause in visual
I select the thread which had the infinite loop instead of the “main thread” which was just waiting (epoll_wait).
I put a breakpoint in the code
I got the timeout window, I said abort command
I resumed, it actually hit my breakpoint
and from there I was able to step.

So I guess switching to the correct thread did the trick?
That kind of solves my issue.

The stepping is extremely slow, it’s taking about 2 seconds each time, is that expected?

Thanks.

[cpuser]

I forgot to mention, I am using a Nexus 7 and VisualGDB 4.0.

[Author]

Posts