I'm investigating the best way to analyse a (Win64, C++, #ue5) minidump these days. Rider doesn't do it (barring .Net), which is a shame. WinDbg is super unfriendly and I hate it. VS works quite well, but I'd rather not rely on it - I only really use the compilers as a back-end these days so don't pay for it.
I feel like a new debug tool was discussed around here recently but I can't remember it for the life of me what it was called or whether it was suited to minidump analysis. Any tips?
@sinbad Not particularly a Microsoftie but I don't think you have to pay for Visual Studio for this use case, Visual Studio Community Edition would work fine last I checked*, unless that's not an option for you because of some limitations in the license?
@sinbad Depending on your use case you could possibly modify CrashReportClient, which does some mini dump analysis with DbgHelp and symbol resolving if available, then output to your own end point/format?
RemedyBG (https://remedybg.itch.io/remedybg) was the one I was trying to remember. It's cool, but it doesn't currently support minidumps unfortunately (I've bought it to try anyway because it's very clever)
Add comment