nohup causes clisp startup to sigsegv

2009-06-12 Thread Karl Berry
Running nohup from coreutils 7.4, GNU clisp crashes on startup:

nohup /home/karl/src/clisp/clisp-build/clisp -q -norc -c 
../../../../../utils/xindy/rte/ordrules/ordrulei.lsp -o ordrulei.fas
nohup: ignoring input and appending output to `nohup.out'
Segmentation fault

The output from clisp is below, indicating stack overflow.  The input
file is tiny (2k) and about as trivial as one can imagine, just making a
few definitions.  Attaching it.  Of course the crash happens with any
lsp input file, as far as I can tell.

It makes no difference whether the nohup is put in the background or not.

I've tried increasing the stack space with ulimit.  No difference.  Not
even the numbers in the crash output about number of bytes allocated/in
use/free change.

Running clisp directly, without nohup, works fine.

Running nohup from coreutils 5.2.1 (actually /usr/bin/nohup Red Hat
WS4) also works fine.  Normal output below also.

Here are the lines around 527 of eval.d:

  /* we used to start a new driver() here, but this is wrong because it
 does not clean up SP  back_trace, just STACK, see
 
https://sourceforge.net/tracker/?func=detailatid=101355aid=1448744group_id=1355
 we probably cannot even do NOTREACHED - the STACK is bad. */
  fprintf(stderr,\n[%s:%d] reset() found no driver frame (sp=0x%x-0x%x)\n,
  __FILE__,__LINE__,(aint)SP_anchor,(aint)SP());
  abort();

This is with clisp 2.44.1 that I compiled myself a year or so ago.  I
don't know if it will reproduce with different versions of clisp, or if
versions of other things might be relevant.

?

Thanks,
Karl

---
Failing output:
*** - Program stack overflow. RESET

[/home/karl/src/clisp/clisp-2.44.1/src/eval.d:527] reset() found no driver 
frame (sp=0xbfffdc00-0xbfffd814)

*** - handle_fault error2 ! address = 0x7019 not in [0x20240004,0x204aadc4) !
SIGSEGV cannot be cured. Fault address = 0x7019.
Permanently allocated: 92096 bytes.
Currently in use: 4194664 bytes.
Free space: 473272 bytes.


--
Successful output:

;; Compiling file 
/home/texlive/karl/Build/source/utils/xindy/rte/ordrules/ordrulei.lsp ...
;; Wrote file 
/home/texlive/karl/Build/source/Work/utils/xindy/rte/ordrules/ordrulei.fas
;; Wrote file 
/home/texlive/karl/Build/source/Work/utils/xindy/rte/ordrules/ordrulei.c
0 errors, 0 warnings




ordrulei.lsp
Description: Binary data
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: nohup causes clisp startup to sigsegv

2009-06-12 Thread Paul Eggert
k...@freefriends.org (Karl Berry) writes:

 Running nohup from coreutils 7.4, GNU clisp crashes on startup:

 nohup /home/karl/src/clisp/clisp-build/clisp -q -norc -c 
 ../../../../../utils/xindy/rte/ordrules/ordrulei.lsp -o ordrulei.fas
 nohup: ignoring input and appending output to `nohup.out'
 Segmentation fault

That's not a nohup bug; it's a clisp bug.  You can reproduce the problem
without using nohup by using the following shell command:

clisp -q -norc -c ordrulei.lsp -o ordrulei.fas 0/dev/null

I just now filed a bug report against GNU clisp, here:

http://sourceforge.net/tracker/?func=detailaid=2805778group_id=1355atid=101355

where it seems to be assigned to Bruno Haible.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils