It simply ignores my breakpoints even though it successfully waits for the debugger. How well does using the lldb command line directly work for you?Īlso note: rust itself ships some pretty printers that you might want to setup.Hey,I think I’m running in this issue nearly every month, and I’m still not really sure what the issue is for this, and I’m also unsure what the fix was the last time since it seems like the issue is different every time.įor some reason, I’m unable to hit breakpoints in my Debug build for Android when starting it with the debugger. I'd like to determine if this is an Android Studio UI issue or lower level. We might be able to help out with low level problems with rust lldb integration (really this was Tom's area, but he is no longer an active contributor). Debugging using this method often takes way more time than debugging C++ code and is very Rahm: Is this something your team handles? This is a very rough flow and I'm sure there are more tips/tricks. From there use run to cursor for getting to the line you want to break at.Continue and breakpoint should hit at beginning of function.In Android studio add symbol breakpoint in lldb debug console: b _symbolnamehere.
Lookup symbol of function you want to break in using for example: > readelf -Ws obj-aarch64-unknown-linux-android/toolkit/library/build/libxul.so | grep pre_update, using regexp if you need finer grain search.lldbinit file in home as documented here. Start Debugger and wait for lldb to break at initial process launch (Only works if you've setup lldb symbol folders in AS and.Looks like rust debugging works in Android Studio, but is a bit cumbersome. (In reply to Kris Taeleman (:kris/kris) from comment #6)
0 kommentar(er)
