Re: errbacktrace
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-07-05T03:24:33Z
Lists: 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
Commits
-
Remove debugging aid
- 45ff049e288b 13.0 landed