Re: PATCH: backtraces for error messages

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: backtraces for error messages
Date: 2018-06-23 12:25:16
Message-ID: CAMsr+YHJdQ86P5DU2fPQ59UabehOi36gtMNozpxY3D8t69K-qw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23 June 2018 at 20:22, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

> Yeah. libunwind doesn't expose any interface to get that information, so
> you'd have to use platform APIs, like glibc's dl_iterate_phdr or dladdr, or
> capture /proc/self/maps.
>

Ahem, I take that part back.

https://stackoverflow.com/a/21584356/398670

see /usr/include/link.h

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-06-23 13:13:28 Re: Incorrect errno used with %m for backend code
Previous Message Craig Ringer 2018-06-23 12:22:19 Re: PATCH: backtraces for error messages