gmane.lisp.cmucl.devel

Re: Small core broken?

,--- I/Alex (Wed, 28 May 2008 23:13:40 -0400) ----*
|
| Will adding
| 
|     (pushnew :small *features*)
| 
| to `tools/setenv-scripts/base-features.lisp' do? Cross-build is not
| needed, right?
|
`-------------------------------------------------*

This didn't work for me, on FreeBSD:

----------------------------------------------------------------------

; Loading #P"XXX/build-2/setenv.lisp".
T
* 
(:NO-CLX :SMALL :GERDS-PCL :PCL-STRUCTURES :PORTABLE-COMMONLOOPS :PCL
...

Loading binary of STRATEGY...
Compiling IMPL...

; Python version 1.1, VM version Intel x86 on 28 MAY 08 11:14:10 pm.
; Compiling: XXX/src/pcl/simple-streams/impl.lisp 06 DEC 04 12:07:05 pm

; Comment: $Header: /project/cmucl/cvsroot/src/pcl/simple-streams/impl.lisp,v 1.7 2004/12/06
17:07:05 rtoy Exp $

(Continue reading)

headers

Raymond Toy | 29 May 05:40

Re: Small core broken?

Alex Goncharov wrote:
>
> Error in function "<error finding name>":  Segmentation Violation at #x47FD7B7C.
>    [Condition of type SIMPLE-ERROR]
>
> Restarts:
>   0: [CONTINUE] Return NIL from load of "target:tools/worldcom".
>   1: [ABORT   ] Return to Top-Level.
>
> Debug  (type H for help)
>
> (C::DO-CALL #<Code Object "DEFUN PRINT-FRAME-CALL-1" {101A65D7}> 24 231 216
>  301948867 ("Tag for DEFUN PRINT-FRAME-CALL-1"))
> Source: 
> ; File: target:code/byte-interp.lisp
> (BYTE-APPLY FUNCTION NUM-ARGS OLD-SP)
> 0]
>
>   
No usable backtrace?   Can't print out the local vars?  If you have gdb 
running, you might be able to find out what function  #x47FD7B7C is in.

Sorry I can't help too much.  I've never had to debug the byte compiler.

Ray

headers

Alex Goncharov | 29 May 05:48

Re: Small core broken?

,--- You/Raymond (Wed, 28 May 2008 23:40:12 -0400) ----*
|
| Alex Goncharov wrote:
| >
| > Error in function "<error finding name>":  Segmentation Violation at #x47FD7B7C.
| >    [Condition of type SIMPLE-ERROR]
| >
| > Restarts:
| >   0: [CONTINUE] Return NIL from load of "target:tools/worldcom".
| >   1: [ABORT   ] Return to Top-Level.
| >
| > Debug  (type H for help)
| >
| > (C::DO-CALL #<Code Object "DEFUN PRINT-FRAME-CALL-1" {101A65D7}> 24 231 216
| >  301948867 ("Tag for DEFUN PRINT-FRAME-CALL-1"))
| > Source: 
| > ; File: target:code/byte-interp.lisp
| > (BYTE-APPLY FUNCTION NUM-ARGS OLD-SP)
| > 0]
| >
| >   
| No usable backtrace?   Can't print out the local vars?  If you have gdb 
| running, you might be able to find out what function  #x47FD7B7C is in.

Actually, I did my run on a "small" build not because I needed a
smaller core, but in an attempt to understand how others might have
done it and what observed.  No strong desire to debug this thing on my
part.

| Sorry I can't help too much.  I've never had to debug the byte compiler.

(Continue reading)