[Not really OT] Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language.

[Richard (Rikki) Andrew Cattermole]

On 22/07/2024 5:42 AM, aberba wrote:
> On Sunday, 21 July 2024 at 17:39:23 UTC, Richard (Rikki) Andrew 
> Cattermole wrote:
>> On 22/07/2024 5:31 AM, aberba wrote:
>>> [...]
>>
>> That covers non-lifetime, non-segfault, and non-assert issues.
>>
>> Unfortunately you cannot rely on using things like signal handlers to 
>> throw an exception, as you may not own the thread let alone the 
>> process to have one.
>>
>> Asserts/boundchecks/null deref these things cannot bring down the 
>> process.
>>
>> This includes for web services too.
>>
>> Imagine trying to explain to somebody that they lost 100k in sales 
>> because the web server they were connected to segfaulted out because 
>> it was written in D and not in an application VM language like Java. 
>> It would go down very well!
> 
> @live?

Within a function body that provides spatial memory lifetime guarantees.

That is the easy part, its inter-function which is the hard part and it 
does not attempt to solve that.

I.e. storing a pointer into some objects and knowing that you have the 
only access to it, and if you extract it you have the only value of it.