Path: ...!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: "White House to Developers: Using C or C++ Invites Cybersecurity
 Risks"
Date: Sat, 9 Mar 2024 14:18:14 -0800
Organization: A noiseless patient Spider
Lines: 36
Message-ID: <usin76$2htsq$2@dont-email.me>
References: <us0brl$246bf$1@dont-email.me> <us1lb5$2f4n4$1@dont-email.me>
 <20240303092938.43@kylheku.com> <us2m8u$2m9mm$1@dont-email.me>
 <us2s0i$2n6h3$5@dont-email.me> <us41kk$327oo$1@dont-email.me>
 <us5bd9$3b404$1@dont-email.me> <us6n21$3mbe2$1@dont-email.me>
 <us80kd$3v39d$1@dont-email.me> <us9hc9$b720$1@dont-email.me>
 <usaq3v$l26r$3@dont-email.me> <usfvld$1tfqm$2@dont-email.me>
 <ushkfm$2ai73$1@dont-email.me> <usin3i$2htsq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 9 Mar 2024 22:18:14 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="0c5e4c226908d988f63fdd2be319dab1";
	logging-data="2684826"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+1A7dAYKtdw5wR686jBjAtfW8NhS49+B0="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:D3NXUJh6RthKdLfDY503uX0JaHw=
Content-Language: en-US
In-Reply-To: <usin3i$2htsq$1@dont-email.me>
Bytes: 2515

On 3/9/2024 2:16 PM, Chris M. Thomasson wrote:
> On 3/9/2024 4:25 AM, David Brown wrote:
>> On 08/03/2024 22:23, Chris M. Thomasson wrote:
>>> On 3/6/2024 2:18 PM, Chris M. Thomasson wrote:
>>>> On 3/6/2024 2:43 AM, David Brown wrote:
>>> [...]
>>>
>>> This is a fun one:
>>>
>>> // pseudo code...
>>> _______________________
>>> node*
>>> node_pop()
>>> {
>>>      // try per-thread lifo
>>>
>>>      // try shared distributed lifo
>>>
>>>      // try global region
>>>
>>>      // if all of those failed, return nullptr
>>> }
>>>
>>
>> Just to be clear here - if this is in a safety-critical system, and 
>> your allocation system returns nullptr, people die.  That is why you 
>> don't use this kind of thing for important tasks.
>>
>>
> 
> In this scenario, nullptr returned means the main region allocator is 
> out of memory. So, pool things up where this never occurs.
> 


You know how to do it! I know you do.