SP Crashing

[Rod Widdowson]

It occurred to me overnight that before you go too far down the build world (which is very much targeted at "Scott or Rod"), you
might get something from a remote debug session.

Assuming you have Visual Studio on a different machine:

* Get the Shib symbols onto the machine with visual studio (it will also need to be connected to the internet to resolve the MS
symbols)
* Get the remote debugging tools installed[1] and started (you'll need to run it elevated) on the machine with shibd.
* On the machine with the symbols and visual studio attach to the shibd.exe on the target machine (Debug->Attach to
process->ConnectionTarget == machine with shibd on it).
* Break in and make sure that all the symbols are resolving (this will take a while as VS downloads the symbols for all the DLL's
that shibd links again)
* let it run and when shibd crashes it should break into the debugger and you might get a clean stack of what the problem is.

However to set expectations the "new improved heap" that has, I think, been in VS since 15 is not (IMO) very helpful on the
diagnosis front and the classic problem with a heap corruption is that it happen very often after the event.

[1] https://visualstudio.microsoft.com/downloads/?q=remote