pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: errbacktrace
Date: Tue, 9 Jul 2019 11:43:28 +0200
Message-ID: <de6cb49b-1969-66f5-ac71-fbff5fd3be25@2ndquadrant.com> (raw)
In-Reply-To: <20190708162851.GA11054@alvherre.pgsql>
References: <20190708162851.GA11054@alvherre.pgsql>

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.

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





view thread (28+ messages)  latest in thread

Message-ID: <de6cb49b-1969-66f5-ac71-fbff5fd3be25@2ndquadrant.com>
Permalink:  ../de6cb49b-1969-66f5-ac71-fbff5fd3be25@2ndquadrant.com/
Also on:    postgresql.org/message-id/de6cb49b-1969-66f5-ac71-fbff5fd3be25@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, alvherre@2ndquadrant.com, 9erthalion6@gmail.com, thomas.munro@gmail.com
  Subject: Re: errbacktrace
  In-Reply-To: <de6cb49b-1969-66f5-ac71-fbff5fd3be25@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox