Re: Optionally using a better backtrace library?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optionally using a better backtrace library?
Date: 2023-07-03 14:26:24
Message-ID: 250d001a-1721-ce0b-888b-db2c29195723@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02.07.23 20:31, Andres Freund wrote:
> A lot of platforms have "libbacktrace" available, e.g. as part of gcc. I think
> we should consider using it, when available, to produce more useful
> backtraces.
>
> I hacked it up for ereport() to debug something, and the backtraces are
> considerably better:

Makes sense. When we first added backtrace support, we considered
libunwind, which didn't really give better backtraces than the built-in
stuff, so it wasn't worth dealing with an additional dependency.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2023-07-03 14:42:58 Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG
Previous Message Vik Fearing 2023-07-03 14:23:50 Re: Add support for AT LOCAL