Re: v2.3.3 and v2.3.4 core dump at gc.c:68

2008-10-05 Thread Henrik Sarvell
What crap, if that is the case I want to change, I still want as little friction as possible which I get from Ubuntu, is there another distro which will give me the same ease of use? Alex, didn't you compile with 4.2.3 on Debian only to see it crash with that one too or am I mistaken? /Henrik

Re: v2.3.3 and v2.3.4 core dump at gc.c:68

2008-10-05 Thread Alexander Burger
On Sat, Oct 04, 2008 at 10:58:58PM +0300, Andrei Ivushkin wrote: Funny enough. I've just downloaded and compiled picolisp-2.3.4 on Zenwalk ... and bad.l script works fine. Good to hear that. I still hope that this bug is restricted to the GCC version distributed with Ubuntu. I quite frequently

Re: v2.3.3 and v2.3.4 core dump at gc.c:68

2008-10-05 Thread Alexander Burger
On Sun, Oct 05, 2008 at 04:34:09PM +0700, Henrik Sarvell wrote: friction as possible which I get from Ubuntu, is there another distro which will give me the same ease of use? Not sure. Ubuntu is really nice, and clever usually when it comes to hardware detection. Knoppix is an alternative,

Re: v2.3.3 and v2.3.4 core dump at gc.c:68

2008-10-04 Thread Alexander Burger
Now I found it! (pool bad.db) (do 200 (new T) (gc)) If you put this into a file named bad.l, and call $ bin/picolisp bad.l Segmentation fault This crashes reproducibly when bin/picolisp was compiled with

v2.3.3 and v2.3.4 core dump at gc.c:68

2008-10-03 Thread Tomas Hlavaty
Hi Alex, I encountered the following problem with GC: === $ gdb ~/picolisp/bin/picolisp ~/picolisp/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change