This is a bug that could also happen in Rust if someone used 'unwrap', or if the code panicked for any other reason. You can have logic bugs in any language. Remember the Cloudflare outage of Nov 2025.
It's also worth noting that the vulnerability you link to is a denial of service vulnerability. While yes, this is technically a vulnerability, it's not the sort of thing that people are usually worrying about in the context of null pointers. If features that give rise to DoS vulnerabilities are the ones to worry about, top of the list would have to be backtracking regex engines: https://owasp.org/www-community/attacks/Regular_expression_D...
And to bring it full-circle, this is the exact same thing I run into with Go. When I mention how nice it is that Lang X has feature Y, someone is quick to point out that either, "You can BUILD that in Go" or, "You don't really need feature Y". We've proven that we don't really NEED compilers either... but I would hate to have to do my job without them.
Nope. The C++ memory models is designed around no hidden/non-deterministic memory allocation.
If you try to allocate 10MB on the stack, that's the dev problem if the program fails, it's not the compiler job to guesstimate whether something will fit there or not (and it's impossible anyway, the compiler can't know all the stack sizes a program will ever run on).
Kind of, at least in France? Our privacy-nefarious laws have been passed by both left- and right-leaning governments. It seems that if there is something the elite agrees upon, it is that the plebeians should be kept in check.
It was definitely not planned with the Soviets, for multiple reasons:
- the Poles of the AK (London government loyal) were not the communist faction (Lublin government loyal), and saw the insurrection as the last chance to get a Poland out of the Soviet sphere of influence post WWII – especially after the publicization of Katyn;
- even if they had wanted, Stalin had zero interest in giving a hand to London-loyal Poles that were in frontal opposition to “his” Lublin-loyal Poles;
- the Germans were not caught flat-footed, they already knew of the insurrection preparations and therefore not only was the city well garrisoned, it would have been in any case, as it was the strategic lock of the area to hold the RKKA on the Vistula;
- and all the above is moot in any case, because the RKKA units that reached the neighborhood of Warsaw in '44 had as many chance of taking the city as the German units that reached Moscow in '41 – they were just spent and at the end of their logistic tail after months of fighting during the Bagration operation, and had no chance of successfully developing an opposed crossing of the Vistula against two Panzerkorps.
So the London-loyal Poles were in a damned if you do, damned if you don't situation, and at least they were able to go with a glorious bang. Like a Marshal said, “c'est magnifique, mais ce n'est pas la guerre”.
> So the London-loyal Poles were in a damned if you do, damned if you don't situation, and at least they were able to go with a glorious bang.
Many argue this uprising is nothing to be proud of and the crime of the leadership with devastating results: ~200k civilians went with this bang, and city completely wiped out.
They had bog-standard CPUs in most of the cases, because their power draw was quite low.
You might be too young to have known that time, but 386/486 just had a tiny heat sink on them and that was all; the real power consumption boom and the serious heat dissipation systems came down the Pentium line.
reply