Thanks for the patch. Running with that I see:
::: Success (:INFODB :READ)
infodb test done
::: Running (:BACKTRACE)
fatal error encountered in SBCL pid 56816(tid 8463872):
fault in heap page 6517 not marked as write-protected
boxed_region.first_page: 0, boxed_region.last_page -1
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> backtrace
Backtrace:
0: Foreign function ldb_monitor, fp = 0xad59138, ra = 0x9425
1: Foreign function lose, fp = 0xad59168, ra = 0x64c1
2: Foreign function gencgc_handle_wp_violation, fp = 0xad591a8, ra
= 0x1444f
3: Foreign function memory_fault_handler, fp = 0xad591c8, ra =
0xfdef
4: Foreign function signal_emulation_wrapper, fp = 0xad591e8, ra =
0x103e6
5: Foreign function os_get_runtime_executable_path, fp =
0xad59218, ra = 0xffd0
6: Foreign function os_get_runtime_executable_path, fp =
0xad595b8, ra = 0xffd0
7: SB-PRETTY::END-LOGICAL-BLOCK
8: (COMMON-LISP::FLET WITH-PRETTY-STREAM-367)
9: SB-IMPL::%PRINT-UNREADABLE-OBJECT
10: (COMMON-LISP::LABELS WITH-CIRCULARITY-DETECTION-BODY-2225)
11: (SB-C::HAIRY-ARG-PROCESSOR COMMON-LISP::PPRINT-FILL)
12: SB-PRETTY::OUTPUT-PRETTY-OBJECT
13: (SB-C::HAIRY-ARG-PROCESSOR COMMON-LISP::PRIN1)
14: SB-DEBUG::ENSURE-PRINTABLE-OBJECT
15: (COMMON-LISP::FLET WITH-PRETTY-STREAM-168)
16: (SB-C::TL-XEP SB-DEBUG::PRINT-FRAME-CALL)
17: (SB-C::TL-XEP SB-DEBUG::MAP-BACKTRACE)
18: (SB-C::HAIRY-ARG-PROCESSOR SB-DEBUG::BACKTRACE)
19: (COMMON-LISP::LAMBDA ())
20: (COMMON-LISP::FLET WITHOUT-INTERRUPTS-BODY-[G856]862)
21: (COMMON-LISP::FLET SB-THREAD::WITH-MUTEX-THUNK)
22: (COMMON-LISP::FLET WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]448)
23: SB-THREAD::CALL-WITH-MUTEX
24: (COMMON-LISP::LAMBDA ())
25: Foreign function call_into_lisp, fp = 0xad59f18, ra = 0x1806c
26: Foreign function funcall0, fp = 0xad59f38, ra = 0x32d6
27: Foreign function new_thread_trampoline, fp = 0xad59f78, ra =
0xe123
28: Foreign function _pthread_start, fp = 0xad59fc8, ra = 0x9215f095
29: Foreign function thread_start, fp = 0xad59fec, ra = 0x9215ef52
On Feb 9, 2009, at 1:16 PM, Gábor Melis wrote:
> On Sábado 07 Febrero 2009, Gábor Melis wrote:
>> On Viernes 06 Febrero 2009, Cyrus Harmon wrote:
>>> I've been seeing this on Darwin:
>>>
>>> ...
>>>
>>> ::: Running (:BACKTRACE)
>>>
>>> fatal error encountered in SBCL pid 49494(tid 8447488):
>>> fault in heap page 7845 not marked as write-protected
>>> boxed_region.first_page: 0, boxed_region.last_page -1
>>>
>>>
>>> Welcome to LDB, a low-level debugger for the Lisp runtime
>>> environment. ldb>
>>
>> I take it builds without problems including the contribs? Backtrace
>> from ldb and gdb may help to diagnose. Nothing that should cause this
>> stands out to me immediately, what would help most is bisecting.
>>
>> That said, I think the logic in gencgc_handle_wp_violation (where
>> this error comes from) is:
>> - potentially subject to visibility problems on
>> write_protected_cleared - racy because of the page is unprotected
>> first and
>> write_protected_cleared is set second
>>
>> I think the compiler is not allowed to reorder os_protect with the
>> flag setting.
>>
>> Anyway, getting free_pages_lock in the else branch should help with
>> both problems. But I don't think this is what happens in practice.
>
> I still doubt that this is being triggerred, but the attached patch
> should allow us to see a bit more clearly.
>
>>
>> Cheers, Gabor
> <handle-
> wp
> .diff
> >
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills
> and code to
> build responsive, highly engaging applications that combine the
> power of local
> resources and data with the reach of the web. Download the Adobe AIR
> SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com_______________________________________________
> Sbcl-devel mailing list
> Sbcl-devel@...
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel
|