Re: errbacktrace - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: errbacktrace
Date
Msg-id CA+hUKGLtuuugSsK6CAMuWmdoNaavWYgR-WZWQqte6XZm8=pvsA@mail.gmail.com
Whole thread Raw
In response to errbacktrace  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: errbacktrace  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-hackers
On Tue, Jun 25, 2019 at 11:08 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> For the implementation, I support both backtrace() provided by the OS as
> well as using libunwind.  The former seems to be supported by a number
> of platforms, including glibc, macOS, and FreeBSD, so maybe we don't
> need the libunwind suport.  I haven't found any difference in quality in
> the backtraces between the two approaches, but surely that is highly
> dependent on the exact configuration.
>
> I would welcome testing in all direction with this, to see how well it
> works in different circumstances.

I like it.

Works out of the box on my macOS machine, but for FreeBSD I had to add
-lexecinfo to LIBS.

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Introduce MIN/MAX aggregate functions to pg_lsn
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] get rid of StdRdOptions, use individual binaryreloptions representation for each relation kind instead