Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: avoiding strdup() Date: Mon, 11 Mar 2024 10:13:12 -0700 Organization: None to speak of Lines: 18 Message-ID: <87edcgzo7r.fsf@nosuchdomain.example.com> References: <87y1ayj6hs.fsf_-_@bsb.me.uk> <87r0gizzuo.fsf@nosuchdomain.example.com> <20240310101101.00001fd4@yahoo.com> <20240310100715.866@kylheku.com> <20240311185039.000066fc@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: dont-email.me; posting-host="803e1d91970c7135fb6b17cffb70db2d"; logging-data="3926617"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+whw99owjRbDpElP5si8ec" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:kidG1B9f5agIz46gWQB2unQqfEQ= sha1:AsvIiYSFwS8tseUWsEh7Sl+NNw4= Bytes: 2229 Michael S writes: [...] > Is there any chance at all that on typical Linux machine (i.e. the one > configured to overcommit virtual memory) strdup() returns NULL? > If it was malloc() I'd say - no chance. For strdup() I'm less sure. strdup() calls malloc(), so strdup() can return NULL if and only if malloc() can return NULL -- but with the additional constraint that you first need to have a string argument to strdup() that's long enough to cause a suffiently large argument to be passed to malloc(). One data point: On my Ubuntu system, malloc(SIZE_MAX) returns NULL for very large arguments (over about 23 GiB in my quick and dirty test). -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Medtronic void Void(void) { Void(); } /* The recursive call of the void */