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

Re: Recent SIGSEGV failures in buildfarm HEAD

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Seneca Cunningham <tentra(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Date: 2006-12-31 17:41:48
Message-ID: 4356.1167586908@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> fwiw - I can trigger that issue now pretty reliably on a fast Opteron
> box (running Debian Sarge/AMD64) with make regress in a loop - I seem to
> be able to trigger it in about 20-25% of the runs.
> the resulting core however looks totally stack corrupted and not really
> usable :-(

Hmm, probably the stack overrun leaves the call stack too corrupt for
gdb to make sense of.  Try inserting "check_stack_depth();" into one
of the functions that're part of the infinite recursion, and then make
check_stack_depth() do an abort() instead of just elog(ERROR).  That
might give you a core that gdb can work with.

I'm still having absolutely 0 success reproducing it on a dual Xeon
... so it's not just the architecture that's the issue.  Some kind of
timing problem?  That's hard to believe too.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Seneca CunninghamDate: 2006-12-31 17:48:38
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Previous:From: Tom LaneDate: 2006-12-31 17:34:01
Subject: Re: Added the word TODO in comments

pgsql-patches by date

Next:From: Seneca CunninghamDate: 2006-12-31 17:48:38
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Previous:From: Stefan KaltenbrunnerDate: 2006-12-31 16:43:45
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD

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