Re: Replacing abort() with __builtin_trap()?
От | Andres Freund |
---|---|
Тема | Re: Replacing abort() with __builtin_trap()? |
Дата | |
Msg-id | 20230702180944.hlwjlvmr3vkhakgq@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Replacing abort() with __builtin_trap()? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Replacing abort() with __builtin_trap()?
|
Список | pgsql-hackers |
Hi, On 2023-07-02 13:55:53 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.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? It does not on linux / x86-64. 2023-07-02 10:52:55.103 PDT [1398197][postmaster][:0][] LOG: server process (PID 1398207) was terminated by signal 4: Illegalinstruction vs today's 2023-07-02 11:08:22.674 PDT [1401801][postmaster][:0][] LOG: server process (PID 1401809) was terminated by signal 6: Aborted It wouldn't be bad for postmaster to be able to distinguish between PANIC and Assert(), but I agree that the non-determinism is a bit annoying. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: