***lloda` is now known as lloda
<wingo>lloda: feel free to push a revert if that's the right thing for you. i would like to fix it but i don't have a lot of cycles right now <lloda>np, I'll push the revert then <lloda>I take that back, I was missing one bisect step <lloda>the bad commit is 0f2f5949a21572fad8355473200c7adc6d74f882 'Better unboxing' which is over my head :-/ <mvdw>How would I go about referencing a expression before evaluating it, say I want to pass (+ 5 3) to a function, but not evaluate it. <mvdw>I should've thought of that. <dsmith-work>wingo: # first bad commit: [c957ec7ab0f0a028910dc737e12191f7bdc1ca93] Use atomics for async interrupts <wingo>can you ulimit -c unlimited and get a "thr apply all bt" on the cores? <dsmith-work>So. I bisect seems to leave the workspace at the last good commit <dsmith-work>wingo: Ok, I have a core dump. What;s the proper gdb invocation? <wingo>gdb libguile/.libs/guile core <dsmith-work>#0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 <dsmith-work>#1 0x00007fb5746d2b55 in scm_pthread_mutex_lock (mutex=<optimized out>) at threads.c:1833 <dsmith-work>#2 0x00007fb5746593a3 in scm_system_async_mark_for_thread (proc=0x1065900, thread=<optimized out>) at async.c:147 <dsmith-work>#3 0x00007fb5746b32c3 in signal_delivery_thread (data=<optimized out>) at scmsigs.c:186