Re: [HACKERS] Show backtrace when tap tests fail - Mailing list pgsql-hackers

From David Steele
Subject Re: [HACKERS] Show backtrace when tap tests fail
Date
Msg-id c85cc804-b312-ea25-15e5-5fb6f8f34926@pgmasters.net
Whole thread Raw
In response to Re: [HACKERS] Show backtrace when tap tests fail  (ilmari@ilmari.org (Dagfinn Ilmari Mannsåker))
List pgsql-hackers
On 9/20/17 6:26 AM, Dagfinn Ilmari Mannsåker wrote:
> Craig Ringer <craig@2ndquadrant.com> writes:
> 
>> On 20 September 2017 at 06:36, David Steele <david@pgmasters.net> wrote:
>>
>>>
>>> I just use:
>>>
>>> $SIG{__DIE__} = sub {Carp::confess @_};
> 
> That is the basic idea behind both Carp::Always and Devel::Confess, but
> they also avoid breaking non-string exceptions (references and objects)
> being thrown and caught.  Devel::Confess jumps through even more hoops
> to add backtraces to these without breaking code catching them.

I see.  My object exceptions are always confessed so this code is just
to catch random die's from parts of the code I can't control.  I have
never seen one of them throw a non-string exception before.

-- 
-David
david@pgmasters.net


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Page Scan Mode in Hash Index
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Page Scan Mode in Hash Index