From: Edi W. <ed...@ag...> - 2004-01-06 00:07:02
|
On 05 Jan 2004 22:06:54 +0100, Wolfgang Jenkner <wje...@in...> wrote: > Possibly not related, but some time ago I had a problem with > building a threaded SBCL which manifested itself in SBCL giving a > 'bad signal number -1' message at warm init and then exiting (so it > didn't hang). It was easy to track this down to a bug in (my build > of) glibc-2.3.1. A test is to run > > #include <stdio.h> > #include <signal.h> > > main () > { > printf("%d\n",SIGRTMIN); > } I get 35 here. Is that good or bad? > Upgrading to glibc-2.3.2 eliminated the bug. SuSE 9.0 has glibc 2.3.2. Don't know if that's the original one or if they've patched it, though. Edi. |