#507 handle_fault SIGSEGV

segfault
closed
Bruno Haible
clisp (525)
5
2011-05-13
2008-11-15
moritz schulte
No

Hi,

just downloaded CLISP-2.47 on my Ubuntu system.
(uname output: Linux kiste 2.6.27-8-generic #1 SMP Thu Nov 6 17:38:14 UTC 2008 x86_64 GNU/Linux).

CLISP crashes after "./configure --cbc build" with the following error message:

*** - handle_fault error2 ! address = 0x0 not in [0x334a22000,0x334cfdee8) !
SIGSEGV cannot be cured. Fault address = 0x0.
GC count: 276
Space collected by GC: 319921952
Run time: 36 934307
Real time: 38 362982
GC time: 2 696167
Permanently allocated: 157640 bytes.
Currently in use: 7518448 bytes.
Free space: 288994 bytes.
make[1]: *** [tests] Segmentation fault
make[1]: Verlasse Verzeichnis '/home/moritz/tmp/clisp-2.47/build/tests'
make: *** [check-tests] Fehler 2

I tried to install an uptodate CLISP since the version shipped with Ubuntu (2.44) crashes with a very similar error message when I run my application.

Thanks for any help,
moritz

PS: it seems it's not possible to report bugs anonymously, which doesn't make it too easy for people not having a SourceForge account to report bugs.

Discussion

  • Sam Steingold
    Sam Steingold
    2011-04-29

    this is the standard request for more information.
    1. what is your platform?
    ("uname -a" on a Unix system)
    compiler version? libc (on Linux)?
    2. where did you get the sources? when?
    (absolute dates are prefered over the relative ones)
    3. how did you build CLISP? (what command, options &c)
    please do a clean build (remove your build directory and
    build CLISP with "./configure --build build" or at least
    do a "make distclean" before "make")
    4. if you are using pre-built binaries, the problem is likely
    to be in the incompatibilities between the platform on which
    the binary was built and yours;
    please try compiling the sources.
    5. what is the output of (lisp-implementation-version)?
    6. what is the value of *features*?
    7. please supply the full output (copy and paste)
    of all the error messages.
    If you cannot build CLISP, you can obviously skip 5 and 6,
    but then you should provide more information in 1.
    please see <http://clisp.cons.org/clisp.html#bugs>
    for more information.
    Thanks.

    PS. This bug report is now marked "pending"
    and will auto-close unless you respond
    (in which case it will auto-re-open).

     
  • Sam Steingold
    Sam Steingold
    2011-04-29

    • status: open --> pending
     
    • status: pending --> closed
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).