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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-12-28 22:16:58 | Re: TODO: GNU TLS |
Previous Message | Stephen Frost | 2006-12-28 21:54:29 | Re: TODO: GNU TLS |
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira de Oliveira | 2006-12-28 22:40:52 | Re: xlog directory at initdb time |
Previous Message | Heikki Linnakangas | 2006-12-28 21:28:48 | Re: Load distributed checkpoint |