search

x64dbg / GleeBug

Debugging Framework for Windows.
MIT License
1.2k stars 39 forks source link

Crash while stepping over - thread is a NULL pointer #52

Open m417z opened 4 years ago

m417z commented 4 years ago

Hi Duncan :)

So I updated x64dbg and accepted the offer to try out the new engine, GleeBug. I've used it for several hours with no apparent issues, until, at some moment, it crashed. I wasn't prepared for troubleshooting so I didn't have symbols and such, but from the location of the crash and the source code it looks like it crashed here on line 26:

https://github.com/x64dbg/GleeBug/blob/9fd62daff16526ece4f5917d1632cd1fa697cf65/GleeBug/Debugger.Process.cpp#L24-L26

with thread holding a NULL pointer.

All I did was smashing F8 to step over.

That's not much, but here's a screenshot of handling the exception as a JIT debugger:

image

mrexodia commented 3 years ago

Thanks for the bug reports, I will get back to GleeBug as soon as I have more time. I was using it for more than a year daily and didn't experience any issues but it seems like it's not as ready as I thought :)

m417z commented 3 years ago

By the way, I was debugging explorer.exe, which usually has a lot of threads, perhaps that's related. Maybe it's possible to create a stress test app with a huge amount of threads to reproduce the problem.