bug#10641: [2.0.3+] start_signal_delivery_thread failure on x86_64-freebsd8.2

2013-03-29 Thread Ludovic Courtès
Andy Wingo skribis: > On Sun 29 Jan 2012 19:00, l...@gnu.org (Ludovic Courtès) writes: > >> Adding printfs shows that the thread calling scm_spawn_thread leaves >> cond_wait before the signal thread has signaled the condition (in >> really_spawn). > > From > http://pubs.opengroup.org/onlinepubs/

bug#10641: [2.0.3+] start_signal_delivery_thread failure on x86_64-freebsd8.2

2013-03-13 Thread Andy Wingo
Hi, On Sun 29 Jan 2012 19:00, l...@gnu.org (Ludovic Courtès) writes: > Adding printfs shows that the thread calling scm_spawn_thread leaves > cond_wait before the signal thread has signaled the condition (in > really_spawn). >From >http://pubs.opengroup.org/onlinepubs/009604599/functions/pthrea

bug#10641: [2.0.3+] start_signal_delivery_thread failure on x86_64-freebsd8.2

2012-01-29 Thread Ludovic Courtès
Hello! For the record, scm_spawn_thread sometimes return #f, instead of a valid thread, when called from start_signal_delivery_thread, itself called from the pthread key destructor. For this reason, I added an assertion check in commit 0f4f2d9a, which gets hit systematically on that platform, for