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

From Joe Conway
Subject Re: Optionally using a better backtrace library?
Date
Msg-id 9c4b5939-2db3-7441-a0f1-56e3953ba461@joeconway.com
Whole thread Raw
In response to Optionally using a better backtrace library?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 7/2/23 14:31, Andres Freund wrote:
> Nice things about libbacktrace are that the generation of stack traces is
> documented to be async signal safe on most platforms (with a #define to figure
> that out, and a more minimal safe version always available) and that it
> supports a wide range of platforms:
> 
> https://github.com/ianlancetaylor/libbacktrace
>    As of October 2020, libbacktrace supports ELF, PE/COFF, Mach-O, and XCOFF
>    executables with DWARF debugging information. In other words, it supports
>    GNU/Linux, *BSD, macOS, Windows, and AIX. The library is written to make it
>    straightforward to add support for other object file and debugging formats.
> 
> 
> The state I currently have is very hacky, but if there's interest in
> upstreaming something like this, I could clean it up.

+1
Seems useful!

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: memory leak in trigger handling (since PG12)
Next
From: David Rowley
Date:
Subject: Re: Making empty Bitmapsets always be NULL