Re: [lockhart@alumni.caltech.edu: Third call for platform testing]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no>
Cc: matthew green <mrg(at)eterna(dot)com(dot)au>, ivan <ivan(at)420(dot)am>, Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [lockhart@alumni.caltech.edu: Third call for platform testing]
Date: 2001-04-05 14:17:43
Message-ID: 16502.986480263@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> CREATE INDEX hash_i4_index ON hash_i4_heap USING hash (random int4_ops);
> + ERROR: cannot read block 3 of hash_i4_index: Bad address
>>
>> "Bad address"? That seems pretty bizarre.

> This is obviously something that shows up on _some_ NetBSD platforms.

If it's reproducible on more than one box then we should look into it.
Am I right to guess that "Bad address" means a bogus pointer handed to
a kernel call? If so, it'll probably take some digging with gdb to find
out the cause. I'd be happy to do the digging if anyone can give me an
account reachable via telnet or ssh on one of these machines.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-04-05 15:45:46 AW: Re: TODO list
Previous Message Tom Lane 2001-04-05 14:08:19 Re: [lockhart@alumni.caltech.edu: Third call for platform testing]