21–30 of 49 posts
What MSFT support policy do you need to have the legendary Raymond Chen take a look at it? I say this because we've reported a bunch of Windows bugs (mainly running Windows under virtualization) and getting them to pay attention at all is an up-hill battle.
If you have to ask, you can't afford it.
Part two: https://devblogs.microsoft.com/oldnewthing/20260626-00/?p=11...
Part 1 was interesting; it isn't clear why he split that into a Part 2 since it adds little to the story and is a paragraph long.
But I would hope that some kind of reverse debugger triggered on one of these crashes would make it pretty simple to say "who wrote this 01".
How big and important third-party vendor must be for Raymond Chen to dissect its coredumps?
When you're at that level in a company, it's rare that someone would be micromanaging what you work on at all times.
Earlier quoted context omitted.
I am, for 20 years now. I do embedded stuff too. Still.
I'm a bit surprised you don't run into things like this then :). Do you use GDB and the like at all? Or do you mean all the windows specific stuff etc, I guess I was more imaging the call stack etc. No insult was intended XD
Always wondered if crash reporting is some kind of shady business. It's good to know it does, at minimum, do what it promises and give valuable crash data to MS.
> The good news for the shell32 team is that they are off the hook; they are the victim. The bad news is that we don’t know who the culprit is. The story of software development through the ages.
When you’ve eliminated all possible explanation, it’s time to pack it in.
Windows COM is super weird and way over engineered.
It still feels like a much more advanced way of sharing compiled libraries between different languages than the current default of "export a C ABI and communicate across the barrier via primitive sticks and stones."
COM isn't perfect but I still find it impressive especially since COM/OLE are 40 years old at this point.