Re: stochastic sparc memprotect failure
Greetings!
Jurij Smakov <jurij@wooyd.org> writes:
> On Thu, Jan 21, 2010 at 04:00:35PM -0500, Camm Maguire wrote:
>> Greetings! GCL and its reverse dependencies makes use of a garbage
>> collection algorithm in which pages are marked read-only with
>> mprotect, segfaults on attempted writes are trapped, pages then
>> remarked read-write, and finally using the separation of read-only and
>> writable pages to accelerate collection.
>>
>> This has worked on sparc for many years, but for the last two or so,
>> when random failures in the expected behavior are causing memory
>> corruption. Disabling the algorithm removes all failures. Yet
>> failures are not fully reproducible, but appear occasionally from run
>> to run when investigating with gdb.
>
> I would be glad to be proven wrong, but it looks like currently there
> are no developers interested in tracking down issues like that. The
> best you can do is probably to disable the advanced gc algorithm for
> sparc.
>
Thanks for the suggestion. It looks like I've found the problem and
fixed it now.
Take care,
> Best regards,
> --
> Jurij Smakov jurij@wooyd.org
> Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
>
>
>
>
--
Camm Maguire camm@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
Reply to: