xusheng

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...

> > 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...

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

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

> > 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...

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

We should also consider offering to launch/attach/connect/connect to debug server based on the current group selected within the debug adapter settings dialog

I tested `112f9f0e8d349858a80dd8c14190e620.exe_ ` and it seems to be just slow:  I will look into other samples when possible as well

Well I see it crashes now: ``` Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/Users/xusheng/capa/capa/main.py", line 1103, in sys.exit(main())...

With the fix https://github.com/mandiant/capa/commit/9dd8b7a86448ff7882966347c755631b4c589f9b, it is no longer crashing due to the IL not being loaded. However, it gets to a different crash: ``` lot of lines omitted ...... DEBUG...