Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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.



Attachment: btpatch
Description: text/plain (1.9 KB)

In response to


pgsql-hackers by date

Next:From: Stephen FrostDate: 2006-12-28 23:10:51
Subject: Re: TODO: GNU TLS
Previous:From: Martijn van OosterhoutDate: 2006-12-28 22:47:35
Subject: Re: TODO: GNU TLS

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group