#54 Cannot make; segmentation fault

segfault
closed-invalid
Sam Steingold
clisp (525)
5
2001-07-25
2001-07-25
Liam Healy
No

Fresh checkout from CVS as of today, following the
directions given as output of the configure command.
When I get to the make step, the output ends with

Compiling file
/usr2/people/healy/languages/lisp/clisp/src/format.lisp ...
*** - handle_fault error2 ! address = 0xC0000013 not
in [0x6800ED08,0x680AA000) !
SIGSEGV cannot be cured. Fault address = 0xC0000013.
make: *** [format.fas] Segmentation fault
make: *** Deleting file `format.fas'

`make check' ends the same way.

Discussion

  • Sam Steingold
    Sam Steingold
    2001-07-25

    Logged In: YES
    user_id=5735

    this is the standard request for more information.
    1. where did you get the sources?
    2. how did you build CLISP (what command, options &c)
    3. what is the output of (lisp-implementation-version)?
    4. what is the value of *features*
    5. please supply the full output (copy and paste) of all the
    error messages.
    Thanks.

     
  • Sam Steingold
    Sam Steingold
    2001-07-25

    • labels: --> clisp
    • milestone: --> segfault
    • assigned_to: nobody --> sds
     
  • Liam Healy
    Liam Healy
    2001-07-25

    Logged In: YES
    user_id=17388

    1. where did you get the sources?
    :pserver:anonymous@cvs.clisp.sourceforge.net:/cvsroot/clisp
    2. how did you build CLISP (what command, options &c)
    cvs update
    ./configure
    cd src
    ./makemake --with-readline --with-gettext
    --with-dynamic-ffi > Makefile
    make config.lisp
    gnuclient config.lisp
    make
    3. what is the output of (lisp-implementation-version)?
    Since make does not complete successfully and CLISP cannot
    be run, this cannot be obtained.
    4. what is the value of *features*
    Since make does not complete successfully and CLISP cannot
    be run, this cannot be obtained.
    5. please supply the full output (copy and paste) of all the
    error messages.
    Compiling file
    /usr2/people/healy/languages/lisp/clisp/src/format.lisp ...
    *** - handle_fault error2 ! address = 0xC0000013 not
    in [0x6800ED08,0x680AA000) !
    SIGSEGV cannot be cured. Fault address = 0xC0000013.
    make: *** [format.fas] Segmentation fault
    make: *** Deleting file `format.fas'

     
  • Sam Steingold
    Sam Steingold
    2001-07-25

    Logged In: YES
    user_id=5735

    I am sorry - I forgot to mention the only important thing -
    "uname -a".
    I do not observe this crash either on Linux or on Solaris,
    so I wonder what your platform is.
    Also, please make a "clean build" with
    $ ./configure --build build
    (using a separate build directory is _very_ good idea)
    or at least with "make clean" before "make".
    Thanks.

     
  • Liam Healy
    Liam Healy
    2001-07-25

    Logged In: YES
    user_id=17388

    Linux shadow.nrl.navy.mil 2.2.14aa1 #8 Tue May 2 16:19:17
    EDT 2000 i686 unknown

    ./configure --build build
    gives the same result

    however,
    make clean

    allows make to run to completion.
    So CLISP can be installed and run and I can answer your
    other questions (which are now moot):
    [1]> (lisp-implementation-version)
    "2.27.1 (released 2001-07-17) (built 3205075639) (memory
    3205075883)"
    [2]> *features*
    (:MK-DEFSYSTEM :CLOS :LOOP :COMPILER :CLISP :ANSI-CL
    :COMMON-LISP :LISP=CL :INTERPRETER
    :SOCKETS :GENERIC-STREAMS :LOGICAL-PATHNAMES :FFI :GETTEXT
    :UNICODE :BASE-CHAR=CHARACTER
    :PC386 :UNIX)

     
  • Sam Steingold
    Sam Steingold
    2001-07-25

    Logged In: YES
    user_id=5735

    this is extremely unusual.
    let me repeat what you did:
    $ rm -rf clisp
    $ cvs co clisp
    $ cd clisp
    $ ./configure --build build
    -- crash --
    $ cd build
    $ make
    $ make check
    tests passed

    is this the case?!
    I do not get this crash on linux-2.2.19/gcc-2.95.2/libc-2.2.3

     
  • Liam Healy
    Liam Healy
    2001-07-25

    Logged In: YES
    user_id=17388

    Not exactly.
    I had a previous cvs checkout, probably 2.26.something.
    I did a
    cvs update
    then ./configure
    etc.
    When that failed and you suggested the
    ./configure --build build
    I did that, then did
    cd src
    make
    etc.
    got the same result.

    Oh I see, the `build' is an argument specifying a (new)
    directory named build. I did not realize I was supposed to
    cd build.

    Anyway the make clean certainly cures it, so it was some
    incompatibility of generated files between the previous
    version and the current version.

     
  • Sam Steingold
    Sam Steingold
    2001-07-25

    • status: open --> closed-invalid
     
  • Sam Steingold
    Sam Steingold
    2001-07-25

    Logged In: YES
    user_id=5735

    okay, the unfortunate reason is that when I added :lines arg
    to write and write-to-string, I had to bump the byte
    interpreter version.