This strange tweet got >25k retweets. The author sounds confident, and he uses lots of hex and jargon. There are red flags though... like what's up with the DEI stuff, and who says "stack trace dump"? Let's take a closer look... 馃У1/n
I mean, that's the debugger view of the faulting instruction, with the relevant register values, he may be sloppy in the wording of 'stack dump' and null pointer, but it's the correct and relevant data..
Well, I am an IT engineer but not a programmer so I would have totally believed him. Except that I wait for a few sources to come to same conclusion before believing anything. But I wouldn鈥檛 have any reason to doubt his analysis BECAUSE of the big words and screenshots 馃ぃ
Additionally to the weird flex "Since I am a professional C++ programmer" he also had an exchange with this guy in the same thread which should be more than enough to know that it's all utter bullshit 馃毄馃毄馃毄