| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: errbacktrace |
| Date: | 2019-07-22 18:19:26 |
| Message-ID: | 3814a094-7dcd-106b-d2ad-7ef78f563356@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| v3-0001-Add-backtrace-support.patch | text/plain | 15.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-22 18:35:32 | Re: using explicit_bzero |
| Previous Message | Peter Eisentraut | 2019-07-22 18:17:17 | Re: using explicit_bzero |