From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
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-02 20:34:40 |
Message-ID: | 9c4b5939-2db3-7441-a0f1-56e3953ba461@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2023-07-02 21:27:25 | Re: Making empty Bitmapsets always be NULL |
Previous Message | Tomas Vondra | 2023-07-02 20:26:35 | Re: memory leak in trigger handling (since PG12) |