[Sbcl-devel] Re: Some NetBSD success w/o linkage tables

[Richard M K. <kr...@pr...>]

On Tue, Sep 14, 2004 at 08:22:09AM +0300, Nikodemus Siivola wrote:
> On Tue, 14 Sep 2004, Richard M Kreuter wrote:
>
> >(2) One test (exhaust.impure.lisp) still fails. The other two tests
> >that were failing under 0.8.14 haven't failed on me yet.
> 
> Wierd: seems that the stack-exhaustion checking isn't working on
> NetBSD then. Is there something special (or known buggy) about
> NetBSD mprotect? (A cursory glance at the man-page doesn't make
> anything seem out of place.)
> 
> Could you post the error and backtrace from exhaust.impure.lisp?

This is what's printed when run from the test harness:

--
//running exhaust.impure.lisp test
; in: LAMBDA NIL
;     (SB-KERNEL:FLOAT-WAIT)
; 
; note: deleting unreachable code
; compilation unit finished
;   printed 1 note
unhandled SIMPLE-ERROR in thread 25746: segmentation violation at #X0


unhandled condition in --disable-debugger mode, quitting
test exhaust.impure.lisp failed, expected 104 return code, got 1
--

And here's what's printed without --disable-debugger:

* (load "exhaust.impure.lisp")
; in: LAMBDA NIL
;     (SB-KERNEL:FLOAT-WAIT)
; 
; note: deleting unreachable code
; compilation unit finished
;   printed 1 note

debugger invoked on a SIMPLE-ERROR in thread 27124:
  segmentation violation at #X80540CE

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.

debugger invoked on a TYPE-ERROR in thread 27124:
  The value NIL is not of type SB-DI:FRAME.

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.

debugger invoked on a TYPE-ERROR in thread 27124:
  The value NIL is not of type SB-DI:FRAME.

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.

debugger invoked on a TYPE-ERROR in thread 27124:
  The value NIL is not of type SB-DI:FRAME.

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.

debugger invoked on a TYPE-ERROR in thread 27124:
  The value NIL is not of type SB-DI:FRAME.

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.
Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
* 
--

Regards,
Richard