xusheng
xusheng
> also, @xusheng6 can we use LLIL instead of MLIL to recover basic blocks, such as here ( > > https://github.com/mandiant/capa/blob/20909c1d9519b12ea0237a944e46691766bd7838/capa/features/extractors/binja/extractor.py#L58 > ) so that we're using LLIL everywhere? I...
Will be addressed by #706
I can also reproduce this on a Virtualbox VM with no network interface configured
Also this has nothing to do with Internet, I tested and found that, as long as there is a network interface, even if it is not attached to anything, the...
This is more complicated than I have expected. It seems a bug in the DbgEng DLLs. I can reproduce this with the dbgsrv.exe that comes with WinDbg as well. However,...
However, using `DebugConnect` seems to require that the access to the engine to be made from the same thread, which our current implementation is violating.
Currently the lldb is built without python support. I will address this in a future release
There is no deep reason on this. I just tried to compile LLDB with the most basic things initially to make it work. So I did not even think about...
The `lldb-server` is not used for regular debugging right now. We will need it in the future when we do remote debugging. For LLDB, we are building 14.0.0. Not sure...
A workaround is to manually calculate the actually address corresponding to`seg:off` and read it directly. It would be nice if we can do it directly