#470 segfault on SIGHUP

segfault
closed-fixed
Sam Steingold
clisp (525)
5
2008-05-22
2008-05-03
Andrew Kroll
No

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...

ftp://ftp.uglyplace.org/pkg_dreams/Slackware-12.0.0/repos/development/clisp/2.44.1/src/

Discussion

1 2 3 .. 6 > >> (Page 1 of 6)
  • Sam Steingold
    Sam Steingold
    2008-05-04

    Logged In: YES
    user_id=5735
    Originator: NO

    This bug report is now marked as "pending"/"works for me".
    This means that we think that we cannot reproduce the problem
    and cannot do anything about it.
    Unless you - the reporter - act within 2 weeks
    (e.g., by submitting a self-contained test case
    or answering our other recent requests),
    the bug will be permanently closed.
    Sorry about the inconvenience -
    we hope your silence means that
    you are no longer observing the problem either.

     
  • Sam Steingold
    Sam Steingold
    2008-05-04

    • assigned_to: haible --> sds
    • status: open --> pending-works-for-me
     
  • Sam Steingold
    Sam Steingold
    2008-05-04

    Logged In: YES
    user_id=5735
    Originator: NO

    unless I have a reproducible test case, there is little I can do.
    it would be nice if you could debug this though.
    first thing you could do is strace/ltrace - it could be useful so that I would look at it and say "hmmm, looks weird, I cannot say anything definite" :-)
    then you could compile CLISP with debugging information, run under gdb (or dump core), and give me the backtrace with the values of the relevant variables.
    http://clisp.cons.org/impnotes/faq.html#faq-debug

     
  • Andrew Kroll
    Andrew Kroll
    2008-05-05

    Logged In: YES
    user_id=2049191
    Originator: YES

    simple to do...
    open your favorite terminal (I'm using konsole, use xterm or whatever you like).
    start up clisp
    close the terminal window
    check dmesg :-)
    it seems consistant for me

    lisp.run[19330]: segfault at 0 ip 08068794 sp bfb76270 error 6 in lisp.run[8048000+18c000]
    lisp.run[19411]: segfault at 0 ip 08068794 sp bf9e48e0 error 6 in lisp.run[8048000+18c000]

    So it's got to be the case of losing it's tty :-)

     
  • Andrew Kroll
    Andrew Kroll
    2008-05-05

    • status: pending-works-for-me --> open-works-for-me
     
  • Andrew Kroll
    Andrew Kroll
    2008-05-05

    strace showing segfault

     
    Attachments
  • Andrew Kroll
    Andrew Kroll
    2008-05-05

    Logged In: YES
    user_id=2049191
    Originator: YES

    Here is the strace :-)

    File Added: trace.clisp.19618

     
  • Sam Steingold
    Sam Steingold
    2008-05-05

    Logged In: YES
    user_id=5735
    Originator: NO

    I cannot reproduce this on fc8 (i386) and fc5 (x86_64).
    the strace says:
    --- SIGHUP (Hangup) @ 0 (0) ---
    --- SIGSEGV (Segmentation fault) @ 0 (0) ---
    i.e., the segfault in triggered by SIGHUP.
    what happens when you send a sighup to the clisp process explicitly?
    i.e.,
    1. start clisp in a window
    2. kill -1 `pidof lisp.run`
    3. what do you see in the window where you started CLISP?
    what I see is
    Exiting on signal 1
    Hangup
    which is correct.
    strace shows no segfault.

     
  • Sam Steingold
    Sam Steingold
    2008-05-05

    • status: open-works-for-me --> pending-works-for-me
     
  • Andrew Kroll
    Andrew Kroll
    2008-05-05

    • status: pending-works-for-me --> open-works-for-me
     
1 2 3 .. 6 > >> (Page 1 of 6)