Re: Need help debugging SIGBUS crashes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "Peter 'PMc' Much" <pmc(at)citylink(dot)dinoex(dot)sub(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Need help debugging SIGBUS crashes
Date: 2026-03-17 21:38:45
Message-ID: 569843.1773783525@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2026-03-17 16:56:48 -0400, Tom Lane wrote:
>> Yeah, it seems likely that there is some additional triggering
>> condition that we don't understand; otherwise there would be more
>> people complaining than just you.

> One issue we've seen in the past (on some other BSD, I think NetBSD?) is
> signal handlers used a C function in a shared library, the function was never
> used before the signal handler, and that dynamic symbol resolution allocated
> memory. Which then contributed to deadlocks and/or corruption of alloctor
> metadata.

Yeah, that sounds familiar. I think I found that while trying to get
PG to run reliably on NetBSD/hppa, but I don't remember any details.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-03-17 21:43:26 Re: EXPLAIN: showing ReadStream / prefetch stats
Previous Message Jonathan Gonzalez V. 2026-03-17 21:37:39 Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode