[clisp-list] Re: Build problem on Debian

[Chris H. <ha...@ve...>]

On Mon, May 24, 2004 at 10:39:29AM -0400, Sam Steingold wrote:
>=20
> $ ./configure --with-debug --build build-g
> $ cd build-g
> $ gdb lisp.run
> (gdb) run -B . -E utf-8 -i init.lisp
>=20
> and report the backtrace.
>=20
> you might also try the CVS HEAD.

Debian kernel 2.2.20, gcc 2.95.4, glibc 2.2.

I did a checkout on 24 May and tried - it builds OK, then bombs during
'make check' with a sigsegv error.

So I did the debug build (sheesh! about 3 hours on my box) and
followed the above instructions.

Ummm, what do you mean by a backtrace?  It starts up, loads a bunch of
stuff, then displays a clisp prompt.

Also, the debug build finishes differently - it displays a message
explaining how to see what tests failed - wanna see my tests/clos.erg?
- while the normal build bombs on a sigsegv error.

One thing caught my eye though:

	.gdbinit:139: Error in sourced command file:
	Function "sigsegv_handler_failed" not defined.

I still have the debug build - I don't want to max out my box for 3
hours again for something I know isn't going to work ;-D - so if you'd
like more info, it'll be here for a little while.

>=20
> Please also do
> $ gcc -o malloc unix/malloc.c
> $ for x in 1000000 100000 10000 1000; do ./malloc $x; done
> $ rm -f malloc
> and send the results here.
>=20

Sent that in a earlier post.

--=20
Good judgment comes from experience. Experience comes from bad
judgment.
- Jim Horning