Re: Recent SIGSEGV failures in buildfarm HEAD

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recent SIGSEGV failures in buildfarm HEAD
Date: 2006-12-29 03:28:28
Message-ID: 27597.1167362908@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Andrew Dunstan wrote:
>> here's a quick untested patch for buildfarm that Stefan might like to try.

> Note that not all core files are named "core". On some Linux distros,
> it's configured to be "core.PID" by default.

And on some platforms, cores don't drop in the current working directory
... but until we have a problem that *only* manifests on such a
platform, I wouldn't worry about that. We do need to look for 'core*'
not just 'core', though.

Don't forget the ulimit point either ... on most Linuxen there won't be
any core at all without twiddling ulimit.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-12-29 03:52:45 Re: WITH support
Previous Message Alvaro Herrera 2006-12-29 03:14:41 Re: Recent SIGSEGV failures in buildfarm HEAD

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-12-29 05:20:47 Re: [BUGS] BUG #2846: inconsistent and confusing
Previous Message Alvaro Herrera 2006-12-29 03:14:41 Re: Recent SIGSEGV failures in buildfarm HEAD