chaoticgd

> I don't know if anybody else agrees, but is there any reason this couldn't be in the debugger? There isn't any particular reason, especially now memory consumption is down...

Got the stack tab working, with some caveats.  The biggest issue is that for some functions the live ranges seem to be invalid. It should be possible to display...

Some further thoughts about integrating this with the debugger window: One challenge I see is how we're going to approach the multiple sources of truth that are the two different...

Little update: I'm still working on this. Building the new data structures and porting my existing code to use them is taking some time. I'll copy it all into this...

This is finally ready for review and testing. Take as long as you want, I'm aware it's ballooned in scope quite a lot.

I have actually found another issue, a recent regression with ~~enum editors~~ (actually the view wasn't updating correctly, which was confusing me). Also wondering about what the best way to...

That should be all the issues found so far sorted. I want all the people who regularly work on the debugger to have a look through the symbol guardian/symbol database...

Aand of course there were more bugs, which are now fixed. I'll continue playing about with it to see I can find any more.

I've been thinking, and I've come to the conclusion that the current design for the SymbolGuardian class is unnecessarily complicated. Specifically how the worker thread that loads the symbol table(s)...

I found some other issues: a memory leak in the old SymbolGuardian implementation caused by me not being able to capture a std::unique_ptr in a std::function, and a performance issue...