Re: Recent SIGSEGV failures in buildfarm HEAD - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Recent SIGSEGV failures in buildfarm HEAD
Date
Msg-id 20061228221525.GB6921@alvh.no-ip.org
Whole thread Raw
In response to Re: Recent SIGSEGV failures in buildfarm HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Recent SIGSEGV failures in buildfarm HEAD  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: TODO: GNU TLS
Next
From: Andrew Dunstan
Date:
Subject: Re: TODO: GNU TLS