Re: Optionally using a better backtrace library? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Optionally using a better backtrace library?
Date
Msg-id 250d001a-1721-ce0b-888b-db2c29195723@eisentraut.org
Whole thread Raw
In response to Optionally using a better backtrace library?  (Andres Freund <andres@anarazel.de>)
List 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.




pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Add support for AT LOCAL
Next
From: "Tristan Partin"
Date:
Subject: Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG