@MSGID: <wwvmsxncw2o.fsf@LkoBDZeT.terraraq.uk>
d51500e4
@REPLY: 3@dont-email.me> f94af01c
@REPLYADDR Richard Kettlewell
<invalid@invalid.invalid>
@REPLYTO 2:5075/128 Richard Kettlewell
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<wwvmsxncw2o.fsf@LkoBDZeT.terraraq.uk>
@RFC-References: 1@dont-email.me>
<ygamsxoixhx.fsf@akutech.de>4@dont-email.me> <ygail8biyxm.fsf@akutech.de>1@dont-email.me>
<ygaedizitb9.fsf@akutech.de>2@dont-email.me>
5Arqz@news.chiark.greenend.org.uk>3@dont-email.me>
@TZUTC: 0100
@PID: Gnus/5.13 (Gnus v5.13) Emacs/27.1
(gnu/linux)
@TID: FIDOGATE-5.12-ge4e8b94
candycanearter07 <no@thanks.net> writes:
> On 9/15/23 08:23, Theo wrote:
>> You could get a SIGABRT if you were trying to free something that was
>> already freed.  Are you sure those are interlocked such that for each
>> i you call strdup() exactly once, and subsequently free() exactly
>> once?  If there was some code path that was breaking out of the loop
>> or similar you might get such behaviour.
>
> I thought double free was a SIGSEGV?

If Glibc detects it you`ll get a diagnostic and SIGABRT.

If it doesn`t detect it then anything could happen - SIGSEGV is just one
possibility.

-- 
https://www.greenend.org.uk/rjk/
--- Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
 * Origin: terraraq NNTP server (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441