#470 segfault on SIGHUP

clisp (525)

May 2 07:14:39 shit kernel: lisp.run[19883]: segfault at 1 ip 08068794 sp bf8d26d0 error 6 in lisp.run[8048000+18c000]

I am use CLISP for a project, unfortunately I can't reveal the code for it, but I can describe the application, and list for you the modules used.

Basically CLISP is loading in as a web application, using the following switches:

#!/usr/bin/clisp -q -q -q -q -norc
then the code...

This is actually a stub to load in FAS's, and execute the actual application.

Modules used are:

asdf Revision: 1.110, with a small modification to not print certain annoyance messages
cl-ppcre 1.3.2
puri 1.5.1
acl-compat dated 2006-01-22 in the Changelog

There is one other module loaded that is part of the project, but it does not segfault any place else.

The only thing I can think of that can cause a similar effect is if STDOUT/STDERR go away, like what would happen on an aborted web page containing lots of data.

If there is something I can do to debug this, please let me know so I can home in on the cause and get to you the information you really need to fix the problem. It's not fatal, just annoying, and the information here says to report segfaults... ;-) And it should be cosmetically cleaned up.

I also notice when building CLISP 2.44.1 that there are many segfaults caused during the build phase...

The exact method of how it is built can be located at the following URL (it's a slackbuild) in case you would like to look at how I build it... Small note on that too, is I had to increase the ulimit to 32768, or else the build fails, you may want to update the size to that during the warning when configuring...



<< < 1 2 3 (Page 3 of 3)
  • Sam Steingold

    Sam Steingold - 2008-05-22
    • summary: lisp.run segfault on 32bit x86 linux --> segfault on SIGHUP
    • status: pending-works-for-me --> closed-fixed
  • Andrew Kroll

    Andrew Kroll - 2008-05-24

    Logged In: YES
    Originator: YES

    I didn't have the time to do any bugtesting for you, Does this mean the bug is fixed and closed now? I checked 2.45, but apears the fix got in too late to be included. I will wait for the next release and let you know if it works for me. Thank you very much :-)

<< < 1 2 3 (Page 3 of 3)

Log in to post a comment.