| Why does the debugger sometimes not select the decompiled class? [message #1866273] |
Fri, 24 May 2024 13:02  |
Eclipse User |
|
|
|
Using Eclipse 2024-03.
I often have to step through code I don't have source for, so I use the Enhanced Class Decompiler. This works fine for viewing classes, but I often run into an annoyance in the debugger. Even though I am viewing the decompiled class in one editor buffer, when the debugger hits a breakpoint, it creates another editor buffer for the class and just says "Source not found", with the "Edit Source Lookup Path" button.
I can muck through it as I can see the line number in the stacktrace, so I go to the decompiled class view and go to that line number. I can still see the variables in the Variables pane, and I can still use the "Step Over" and related actions. As I do that, I can watch the line number in the stacktrace change. If it goes to another method, or even another class, I can go to that line number or the other decompiled class, but it's really annoying to have to do this.
I thought perhaps this has something to do with file associations. I ensured that "Class Decompiler Viewer" is set as the default "Associated editor" for both "*.class" and "*.class without source".
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07269 seconds
Home