Re: errbacktrace - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: errbacktrace
Date
Msg-id 3814a094-7dcd-106b-d2ad-7ef78f563356@2ndquadrant.com
Whole thread Raw
In response to Re: errbacktrace  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: errbacktrace  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: errbacktrace  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: errbacktrace  (Thomas Munro <thomas.munro@gmail.com>)
Re: errbacktrace  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2019-07-09 11:43, Peter Eisentraut wrote:
> After further research I'm thinking about dropping the libunwind
> support.  The backtrace()/backtrace_symbols() API is more widely
> available: darwin, freebsd, linux, netbsd, openbsd (via port), solaris,
> and of course it's built-in, whereas libunwind is only available for
> linux, freebsd, hpux, solaris, and requires an external dependency.

Here is an updated patch without the libunwind support, some minor
cleanups, documentation, and automatic back traces from assertion failures.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: using explicit_bzero
Next
From: Tom Lane
Date:
Subject: Re: using explicit_bzero