Disassembly unreadable after starting debugger

[Rainson12]

I am a bit lost. When using binja to check a binary, the assembler code is just fine. However when launching the assembly using the debugger, all the disassembly code is gone and also no breakpoints are hit (probably because the remote address is incorrectly calculated?).

Before:

After starting the debugger:

There is also no analysis happening. I am a bit lost, what do i need to do in order to get back the assembkly code + actually triggering the breakpoint?

[xusheng6]

The disassembly is unavailable because the target is running, so the memory is not readable, and the attempt to disassemble just fails. You can interrupt the target by pressing the "Pause" button and it will become available.

There is still a problem that the entry breakpoint is not hit. For that, could you please let me know how you are configuring the debugger? Did you change default settings?

[Rainson12]

The disassembly is unavailable because the target is running, so the memory is not readable, and the attempt to disassemble just fails. You can interrupt the target by pressing the "Pause" button and it will become available.

There is still a problem that the entry breakpoint is not hit. For that, could you please let me know how you are configuring the debugger? Did you change default settings?

thank you for the quick reply. I didnt change any of the default settings. Putting the debugger on pause will cause this:

In the launch options i did set this as I am trying to debug some functions of a dll used by the exe:

[xusheng6]

The disassembly is unavailable because the target is running, so the memory is not readable, and the attempt to disassemble just fails. You can interrupt the target by pressing the "Pause" button and it will become available.
There is still a problem that the entry breakpoint is not hit. For that, could you please let me know how you are configuring the debugger? Did you change default settings?

thank you for the quick reply. I didnt change any of the default settings. Putting the debugger on pause will cause this:

yeah, when the target is stopped, the memory is being read properly. Another bug prevents the disassembly from showing up. If you simply right-click on the function, and do "Reanalyze the current function", it will probably be fixed. The bug that prevents the disassembly from showing up is fixed on the latest dev

[Rainson12]

The disassembly is unavailable because the target is running, so the memory is not readable, and the attempt to disassemble just fails. You can interrupt the target by pressing the "Pause" button and it will become available.
There is still a problem that the entry breakpoint is not hit. For that, could you please let me know how you are configuring the debugger? Did you change default settings?

thank you for the quick reply. I didnt change any of the default settings. Putting the debugger on pause will cause this:

yeah, when the target is stopped, the memory is being read properly. Another bug prevents the disassembly from showing up. If you simply right-click on the function, and do "Reanalyze the current function", it will probably be fixed. The bug that prevents the disassembly from showing up is fixed on the latest dev

hm not sure what I am doing wrong. Using ollydbg the breakpoints are hit instantly after launching. The function analysis also takes forever (I stopped it after 10 minutes), the dll itself is analyised within a couple seconds. Guess I will have to jump to ghidra to properly debug.

[xusheng6]

Would it be possible to share the binaries with me so that I can see what went wrong?

[xusheng6]

There is probably only one bug that prevents the target from stopping at the entry breakpoint, then things just pile up

[Rainson12]

Would it be possible to share the binaries with me so that I can see what went wrong?

unfortunately the application setup is huge and installation not that easy so I guess its not worth the time. I can share with you further details via discord in case you are interested (username: rainson12). Otherwise I just might wait for the next release and try it again, really appreciate your efforts!

[xusheng6]

Would it be possible to share the binaries with me so that I can see what went wrong?

unfortunately the application setup is huge and installation not that easy so I guess its not worth the time. I can share with you further details via discord in case you are interested (username: rainson12). Otherwise I just might wait for the next release and try it again, really appreciate your efforts!

Are you using the free version? If not, you can switch to use the dev version, which I believe have most, if not all, of the above issues fixed already

[xusheng6]

Closing this due to inactivity. Also this is likely a bug in the last stable's debugger memory cache management that has been fixed