Search
8:07:23
galdor
working on improving code generation depending on the type ?
13:51:41
stassats
::: Running ATOMIC-UPDATE
13:51:41
Colleen
Unknown command. Possible matches: 8, set, say, mop, get, login, grant, time, tell, roll,
13:51:41
stassats
./subr.sh: line 6: 57980 Segmentation fault: 11
13:51:53
stassats
naturally, not reproducible
14:17:28
flip214
dmesg might at least give you the RIP
14:17:33
pfdietz
I did not see any failures on the recent modular arithmetic changes.
15:09:20
stassats
caught another corruption, this time with a cor
15:28:30
stassats
at least now it's in an impure test
15:32:21
stassats
happening not readily but reliably
15:33:57
stassats
stop reason = signal SIGSTOP what does that mean
15:53:38
stassats
not fast enough to perform bisection
16:03:09
stassats
2.5 minutes sometimes to a failure, not good enough to know whether it succeeds or not
16:09:13
stassats
8 minutes in another case
16:12:06
stassats
the common thing, one of the threads is in libsystem_pthread.dylib`_pthread_terminate
16:17:57
stassats
is it the same problem as on openbsd - unable to reclaim the thread stack before it exits?
16:18:12
stassats
new test case, less than 10 seconds to failure