Re: Replacing abort() with __builtin_trap()?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replacing abort() with __builtin_trap()?
Date: 2023-07-02 17:55:53
Message-ID: 183981.1688320553@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> I'd like to propose that we do a configure test for __builtin_trap() and use
> it, if available, before the abort() in ExceptionalCondition(). Perhaps also
> for PANIC, but it's not as clear to me whether we should.

Does that still result in the same process exit signal being reported to
the postmaster? The GCC manual makes it sound like the reported signal
could be platform-dependent, which'd be kind of confusing.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-07-02 18:09:44 Re: Replacing abort() with __builtin_trap()?
Previous Message Andres Freund 2023-07-02 17:41:07 Replacing abort() with __builtin_trap()?