Crash while stepping over - thread is a NULL pointer

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:

GleeBug/GleeBug/Debugger.Process.cpp

Lines 24 to 26 in 9fd62da

    
           void Process::StepOver(const StepCallback & cbStep) 
        
           { 
        
               auto gip = Registers(thread->hThread, CONTEXT_CONTROL).Gip();

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:

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 :)

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.

	void Process::StepOver(const StepCallback & cbStep)
	{
	auto gip = Registers(thread->hThread, CONTEXT_CONTROL).Gip();