I see posts like this, this deep dive into the call stacks and am always humbled and reminded of the limits of my knowledge about computers and programs.

▲

rramadass a minute ago | parent | next [-]

These sort of bugs require a lot of knowledge about a) Windows Internals b) Tools to debug at that level. Most application-level programmers won't need nor are exposed to these.

However, if you are interested in knowing what is all involved, see; Advanced Windows Debugging by Mario Hewardt and Daniel Pravat - https://advancedwindowsdebugging.com/

Review of the book by Raymond Chen himself! - https://devblogs.microsoft.com/oldnewthing/20071218-01/?p=24...

▲

Panzer04 4 hours ago | parent | prev | next [-]

Not a programmer?

▲

kumarvvr 3 hours ago | parent [-]

I am, for 20 years now. I do embedded stuff too. Still.

▲

Panzer04 3 hours ago | parent [-]

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

	▲	FartyMcFarter 3 hours ago \| parent \| next [-]
		As someone who has debugged his fair share of tricky low-level issues, the parts that I find impressive in his blog posts are things such as "then we look at the bytes in memory and oh yeah, this looks like an exception record". I would usually not think to do that (or be able to recognise it as easily as I presume he did).
	▲	kumarvvr 3 hours ago \| parent \| prev \| next [-]
		I have done everything from desktop apps to web apps and a bunch in between. Regular debugging is good enough for me. Never had the need to go down into call stack level. Even with embedded programming, regular C debugger has always been enough.
	▲	2 hours ago \| parent \| prev [-]
		[deleted]

▲

dist-epoch 3 hours ago | parent | prev [-]

Goes both ways, author probably knows little about FPGA programming, React or PyTorch.