Re: Solaris ASM problem - Mailing list pgsql-hackers

From Theo Schlossnagle
Subject Re: Solaris ASM problem
Date
Msg-id 44528993.2040508@omniti.com
Whole thread Raw
In response to Re: Solaris ASM problem  (Kris Jurka <books@ejurka.com>)
List pgsql-hackers
Kris Jurka wrote:

>
>
> On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
>
>> The file that uses the spinlocks:
>> /src/backend/storage/lmgr/s_lock.c
>>
>> can be compiled standalone with -DS_LOCK_TEST
>>
>
> To get the test to compile I had to link in tas.o as the attached 
> patch shows.  Unfortunately this doesn't work for platforms that don't 
> have a tas.o, bailing out with file not found.  Perhaps it's not 
> important to fix this test, but I thought I'd mention it.
>
> Anyway the test exits with
>
> Stuck spinlock (80618e9) detected at ./s_lock.c:355.
>
> on a linux gcc build this exits with
>
> Stuck spinlock (0x5013ad) detected at ./s_lock.c:402.

This seems like a different problem, no?  The patch I sent in didn't 
touch any of the linux assembly bits.  The linux test should pass to the 
end without an issue right?

-- 
// Theo Schlossnagle
// Principal Engineer -- http://www.omniti.com/~jesus/
// Ecelerity: Run with it. -- http://www.omniti.com/



pgsql-hackers by date:

Previous
From: Theo Schlossnagle
Date:
Subject: Re: Solaris ASM problem
Next
From: "Dave Page"
Date:
Subject: Re: stdout when running as a Windows service