Displaying 4 results from an estimated 4 matches for "wrap_osspinlocklock".
2016 Jan 22
4
greendragon build noisy due to mmap_stress.cc
...n 22, 2016 at 4:11 PM, Kuba Brecka <jbrecka at apple.com> wrote:
>> Hm, I tried to reproduce this as well, but unsuccessfully. From the crash
>> report: EXC_I386_GPFLT means we’re dereferencing a non-canonical pointer,
>> in this case “0x00486000000025df”. This happens at wrap_OSSpinLockLock+17,
>> which is just after the prologue and just after calling cur_thread(). So
>> I’d say it happens when we’re dereferencing the pointer returned by
>> cur_thread(). On OS X, we’re doing this trick where we store the
>> ThreadState pointer in the shadow memory. Could it...
2016 Jan 22
2
greendragon build noisy due to mmap_stress.cc
Hm, I tried to reproduce this as well, but unsuccessfully. From the crash report: EXC_I386_GPFLT means we’re dereferencing a non-canonical pointer, in this case “0x00486000000025df”. This happens at wrap_OSSpinLockLock+17, which is just after the prologue and just after calling cur_thread(). So I’d say it happens when we’re dereferencing the pointer returned by cur_thread(). On OS X, we’re doing this trick where we store the ThreadState pointer in the shadow memory. Could it be that something actually read/wro...
2016 Jan 21
2
greendragon build noisy due to mmap_stress.cc
...rt.tsan_osx_dynamic.dylib 0x00000001063952e5 __tsan_thread_start_func + 69
4 libsystem_pthread.dylib 0x00007fff93b5bfd7 _pthread_start + 176
5 libsystem_pthread.dylib 0x00007fff93b593ed thread_start + 13
Thread 21 Crashed:
0 libclang_rt.tsan_osx_dynamic.dylib 0x00000001063cbe01 wrap_OSSpinLockLock + 17
1 libsystem_pthread.dylib 0x00007fff93b5bfd7 _pthread_start + 176
2 libsystem_pthread.dylib 0x00007fff93b593ed thread_start + 13
Thread 21 crashed with X86 Thread State (64-bit):
rax: 0x00486000000025df rbx: 0x00000001095ea000 rcx: 0x00486000000025df rdx: 0x000000000000...
2016 Jan 20
2
greendragon build noisy due to mmap_stress.cc
On Wed, Jan 20, 2016 at 1:31 PM, Chris Matthews <chris.matthews at apple.com>
wrote:
> I worded that poorly, the Jenkins check I added will explain to the user
> that we know this fails sometimes.
>
> On Jan 20, 2016, at 1:30 PM, Chris Matthews <chris.matthews at apple.com>
> wrote:
>
> I have added a Jenkins check for this test, which explains why it fails on