Steel Bank Common Lisp

Edi Weitz wrote:
> the build process hangs forever and CPU usage (kernel) approaches
> 100%. Any idea what could be the cause?

That occurred to me the one time I tried to build SBCL 0.8.6.something
on SuSE AMD64 Pro 9 using :sb-thread.

> 2. Try building without thread support?

I've successfully built many versions of SBCL on SuSE AMD64 Pro 9
without thread support.

Kevin

Edi Weitz <edi@...> writes:

> the build process hangs forever and CPU usage (kernel) approaches
> 100%. Any idea what could be the cause?
> 
> The file customize-target-features.lisp looks like this
> 
>   (lambda (list)
>     (adjoin  :sb-thread list))

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);
}

Upgrading to glibc-2.3.2 eliminated the bug.

Wolfgang

On 05 Jan 2004 22:06:54 +0100, Wolfgang Jenkner <wjenkner@...> 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.

On Sun, 4 Jan 2004 18:50:20 -0700, Kevin Rosenberg <kevin@...> wrote:

> Edi Weitz wrote:
>> the build process hangs forever and CPU usage (kernel) approaches
>> 100%. Any idea what could be the cause?
>
> That occurred to me the one time I tried to build SBCL
> 0.8.6.something on SuSE AMD64 Pro 9 using :sb-thread.
>
>> 2. Try building without thread support?
>
> I've successfully built many versions of SBCL on SuSE AMD64 Pro 9
> without thread support.

Yes, I can confirm that it builds without thread support. What could
be the cause? Is this related to the SIGRTMIN problem?

Of course, I'd like to have thread support... :(

Thanks,
Edi.

Edi Weitz <edi@...> writes:

> [test for the presence of a particular bug]
> I get 35 here. Is that good or bad?

Good.  Or bad, since this means that you have a different problem.
Sorry that this didn't help.

Wolfgang

Edi Weitz <edi@...> writes:

> On Sun, 4 Jan 2004 18:50:20 -0700, Kevin Rosenberg <kevin@...> wrote:
>
>> Edi Weitz wrote:
>>> the build process hangs forever and CPU usage (kernel) approaches
>>> 100%. Any idea what could be the cause?
>>
>> That occurred to me the one time I tried to build SBCL
>> 0.8.6.something on SuSE AMD64 Pro 9 using :sb-thread.
>>
>>> 2. Try building without thread support?
>>
>> I've successfully built many versions of SBCL on SuSE AMD64 Pro 9
>> without thread support.
>
> Yes, I can confirm that it builds without thread support. What could
> be the cause? Is this related to the SIGRTMIN problem?
>
> Of course, I'd like to have thread support... :(

This just happened to me, too :-/

Are you running a 2.6.x kernel, or a kernel otherwise with NPTL (the
new Posix threads implementation)?  If so, try adding :sb-futex as
well as :sb-thread to *features* (though no guarantees, I'm afraid).

Cheers,

Christophe
-- 
http://www-jcsu.jesus.cam.ac.uk/~csr21/       +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%")    (pprint #36rJesusCollegeCambridge)

On Wed, 07 Jan 2004 11:54:05 +0000, Christophe Rhodes <csr21@...> wrote:

> Edi Weitz <edi@...> writes:
>
>> Of course, I'd like to have thread support... :(
>
> This just happened to me, too :-/
>
> Are you running a 2.6.x kernel, or a kernel otherwise with NPTL (the
> new Posix threads implementation)?  If so, try adding :sb-futex as
> well as :sb-thread to *features* (though no guarantees, I'm afraid).

The kernel is 2.4.21 but maybe they've patched it. I have the files

  ./kernel/futex.c
  ./include/linux/futex.h

in /usr/src/linux - does that mean something?

I'll try and report to the list.

Thanks,
Edi.

On Wed, 07 Jan 2004 13:22:37 +0100, Edi Weitz <edi@...> wrote:

> I'll try and report to the list.

Unfortunately, it seems to hang at the same place:

  [building initial core file in "output/cold-sbcl.core":
  writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :READ-ONLY>
  writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :STATIC>
  writing 34848768 bytes [8508 pages] from #<SB!FASL::GSPACE :DYNAMIC>
  /(DESCRIPTOR-BITS INITIAL-FUN)=#XA3A4465
  done]
  * //testing for consistency of first and second GENESIS passes
  //header files match between first and second GENESIS -- good
  //entering make-target-2.sh
  //doing warm init
  This is SBCL 0.8.7, an implementation of ANSI Common Lisp.

  More information about SBCL is available at <http://www.sbcl.org/>.
  SBCL is free software, provided as is, with absolutely no warranty.
  It is mostly in the public domain; some portions are provided under
  BSD-style licenses.  See the CREDITS and COPYING files in the
  distribution for more information.

Edi Weitz <edi@...> writes:

> The kernel is 2.4.21 but maybe they've patched it. I have the files
>
>   ./kernel/futex.c
>   ./include/linux/futex.h
>
> in /usr/src/linux - does that mean something?

Hed Rat ships 2.4 kernels with NPTL patched in. If you're running an
RH system then you probably do have it.

-- 
James A. Crippen <james at unlambda.com> Lambda Unlimited
61.2204N, -149.8964W                     Recursion 'R' Us
Anchorage, Alaska, USA, Earth            Y = \f.(\x.f(xx))(\x.f(xx))

On Wed, 07 Jan 2004 11:44:13 -0900, james@... (James A. Crippen) wrote:

> Edi Weitz <edi@...> writes:
>
>> The kernel is 2.4.21 but maybe they've patched it. I have the files
>>
>>   ./kernel/futex.c
>>   ./include/linux/futex.h
>>
>> in /usr/src/linux - does that mean something?
>
> Hed Rat ships 2.4 kernels with NPTL patched in. If you're running an
> RH system then you probably do have it.

No, as I mentioned a couple of mails ago this is SuSE 9.0.

Edi.