Gabriele Digregorio

I have a couple of observations: 1. Did you evaluate the possibility of choosing the mode at memory access time rather than during the startup of the debugger? There are...

> Choosing the mode at access time would multiply the amount of syscalls we need to do this, as at every access we would need to perform open+seek+read+close. It's probably...

> I personally see this feature as opt-in just for now, if we don't observe any drawbacks I'd propose to switch the default to fast_memory=True and keep the ptrace implementation...

> So you are proposing something like d.memory going through ptrace and d.fast_memory using proc/pid/mem? What would the benefit of two different views be? The benefits are the same as...

Hi @MarcoMeinardi , clutch request—this is the project glow-up we needed. I’m on it. `Debugger.llm()` will be released soon, and I’ll add a mechanism to auto-swat any rogue `Debugger.recvline()` calls....

Note: the same should be done for t.regs and thread_context

I discussed the problem with @MrIndeciso and we tested the code you proposed. It really seems to be a race condition. The point is that the attachment of libdebug is...

I will close this issue since it is not something we can control. As @Frank01001 mentioned, we have included a warning in the documentation about this behavior, which is the...