public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter 'PMc' Much <[email protected]>
To: Tomas Vondra <[email protected]>
Cc: [email protected]
Subject: Re: Need help debugging SIGBUS crashes
Date: Tue, 17 Mar 2026 15:29:51 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Tue, Mar 17, 2026 at 02:40:24PM +0100, Tomas Vondra wrote:
! I agree it's hard to deduce anything from the backtraces with the
! interesting bits optimized out. Rebuilding the OS with -O0 might be an
! overkill, I'd probably start by building just Postgres. That'd at least
! give us some idea what happens there, you could inspect the memory
! context etc.
! 
! I'm not a FreeBSD expert, but this seems a bit suspicious:
! 
!     frame #23: 0x0000000822ae79b6
! libthr.so.3`handle_signal(actp=0x0000000820c5c600, sig=30,
! info=0x0000000820c5c9f0, ucp=0x0000000820c5c680) at thr_sig.c:318:3
!     frame #24: 0x0000000822ae6eba libthr.so.3`thr_sighandler(sig=30,
! info=0x0000000820c5c9f0, _ucp=0x0000000820c5c680) at thr_sig.c:261:2
! 
! I mean, libthr seems to be a 1:1 with pthreads. Are you using threads in
! some way? Perhaps an extension using threads? That could cause weird
! failures, including weird SIGBUS ones.

Hi, thanks for noting this - I didn't look that far up the stack.

The only extensions in this specific cluster are pg_freespacemap and
plpgsql. Others may have hstore and plpython3u.

I have currently no clue where this could come from, but will keep
it in mind. Thank You for noticing it.

PMc

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Need help debugging SIGBUS crashes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox