Re: more backtraces - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: more backtraces
Date
Msg-id b43b4c1e-1a52-008f-a188-bd1fbce5aaf8@2ndquadrant.com
Whole thread Raw
In response to Re: more backtraces  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: more backtraces  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2019-12-04 22:34, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
>> It'd be bad if the addition of backtraces for SEGV/BUS suddenly made it
>> harder to attach a debugger and getting useful results.
> 
> Yeah.  TBH, I'm not sure I want this, at least not in debug builds.

I understand that the SEGV/BUS thing can be a bit scary.  We can skip it.

Are people interested in backtraces on abort()?  That was asked for in 
an earlier thread.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: remove support for old Python versions
Next
From: Peter Eisentraut
Date:
Subject: Re: Remove configure --disable-float4-byval and--disable-float8-byval