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

Re: Recent SIGSEGV failures in buildfarm HEAD

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 22:15:25
Message-ID: 20061228221525.GB6921@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:

> Actually ... one way that a "memory overconsumption" bug could manifest
> as sig11 would be if it's a runaway-recursion issue: usually you get sig11
> when the machine's stack size limit is exceeded.  This doesn't put us
> any closer to localizing the problem, but at least it's a guess about
> the cause?
> 
> 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


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-12-28 22:16:58
Subject: Re: TODO: GNU TLS
Previous:From: Stephen FrostDate: 2006-12-28 21:54:29
Subject: Re: TODO: GNU TLS

pgsql-patches by date

Next:From: Euler Taveira de OliveiraDate: 2006-12-28 22:40:52
Subject: Re: xlog directory at initdb time
Previous:From: Heikki LinnakangasDate: 2006-12-28 21:28:48
Subject: Re: Load distributed checkpoint

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