Note that I am using vanilla eclipse debugging. Now if there's no breakpoint on run(), it doesn't matter whether I continue or step the thread executes. The thread doesn't seems to execute, and my breakpoint in the thread's run() never trips. If I step over, though, I can step over the calls to start(), println(), and join(), after which the program waits for execution to finish, but that never happens. Essentially, when I put a breakpoint on my call to a thread's start() method, as well as on that thread's run() method, things are fine if I "continue" in the debugger. n Hello world Process 28473 stopped thread 1, queue -thread, stop reason step over frame 0: 0x00000001000012f0 terminator.kexe. What you'll need A computer with Android studio installed. Add variables to the Watches pane to aid with debugging. Add conditional expressions to breakpoints to save time debugging. Use breakpoints to pause a running app and inspect the code one line at a time. Below, I've included a test program demonstrating my issue. Currently, the Kotlin/Native compiler produces debug info compatible with the DWARF 2 specification, so modern debugger tools can perform the following operations. How to attach the debugger to your running app. I'm running into a problem new to me when trying to debug a multithreaded program.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |