Re: Recent SIGSEGV failures in buildfarm HEAD

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Date: 2006-12-28 23:01:03
Message-ID: 45944CAF.5070401@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Alvaro Herrera wrote:
> Tom Lane wrote:
>
>
>>
>> I wonder whether there's any way to get the buildfarm script to report a
>> stack trace automatically if it finds a core file left behind in the
>> $PGDATA directory after running the tests. Would something like this
>> be adequately portable?
>>
>> if [ -f $PGDATA/core* ]
>> then
>> echo bt | gdb $installdir/bin/postgres $PGDATA/core*
>> fi
>>
>
> gdb has a "batch mode" which can be useful:
>
> if [ -f $PGDATA/core* ]
> then
> gdb -ex "bt" --batch $installdir/bin/postgres $PGDATA/core*
> fi
>
>

here's a quick untested patch for buildfarm that Stefan might like to try.

cheers

andrew

Attachment Content-Type Size
btpatch text/plain 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2006-12-28 23:10:51 Re: TODO: GNU TLS
Previous Message Martijn van Oosterhout 2006-12-28 22:47:35 Re: TODO: GNU TLS

Browse pgsql-patches by date

  From Date Subject
Next Message Jaime Casanova 2006-12-29 00:20:35 Re: Tablespace for temporary objects and sort files
Previous Message Simon Riggs 2006-12-28 22:47:23 Re: pg_standby