Re: random crashes on -HEAD for a few days now

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: random crashes on -HEAD for a few days now
Date: 2007-08-20 14:19:10
Message-ID: 46C9A2DE.6040603@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> at least one of my buildfarm members (emu) is crashing on what seems
>> totally unrelated regression tests for a few days now:
>
> I was wondering about that ...
>
>> it took me about 10 tries to reproduce that manually and I'm getting the
>> following stacktrace:
>
>> #0 varbit_out (fcinfo=0x88c75000) at varbit.c:549
>> 549 x = *sp;
>
> Just eyeballing that code, it looks like it will try to fetch the byte
> immediately beyond the end of the bit array, when the number of bits is
> an exact multiple of 8. This is unlikely to cause a problem but it
> *could* happen that the input is right up against the end of memory.
> Could you check whether that is what happened here? (The important
> question is whether the input seems to be sane, ie, "len" isn't huge.)

"end of memory" sounds familiar to:

http://archives.postgresql.org/pgsql-hackers/2005-06/msg00819.php

which is how emu is (still) set up.

as for len it seems to be 0:

#0 varbit_out (fcinfo=0x88c75000) at varbit.c:549
s = (VarBit *) 0x88c75000
result = 0x84d33128 ""
r = 0x84d33128 ""
sp = (bits8 *) 0x88c75000 <Address 0x88c75000 out of bounds>
x = 0 '\0'
i = 0
k = 0
len = 0

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lodewijk Vöge 2007-08-20 14:21:48 Re: INSERT/SELECT and excessive foreign key checks
Previous Message Tom Lane 2007-08-20 14:09:38 Re: Why NESTED LOOP Not Allowed for FULL and RIGHT Join.