gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: interrupts in 64-bit GCL


From: Camm Maguire
Subject: [Gcl-devel] Re: interrupts in 64-bit GCL
Date: Fri, 20 Feb 2009 20:58:49 -0500
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Greetings!  I suspect a missing signal block around some code that
needs protecting.  I've reprodced under gdb, but there are no
debugging symbols in the image.  [ Question for list -- have computers
now become so fast that -g should be included by default in all gcl
images? It used to slow down the compiler, don't know about now.  It
does make the image quite a bit bigger. ]

Ideally, you or someone else at the site might be so kind as to
rebuild atop

1) a gcl build with --enable-debug.  If this does not reproduce, then
in addition
2) rebuild atop a standard gcl with the CFLAGS environment variable
set to -g before configure and make.  Please make sure -g is included
in the gcc calls.  Otherwise, makedefs can be modified after configure
and before make to include -g wherever one sees -O3 or -O

Would this be too much trouble?

Take care,

Matt Kaufmann <address@hidden> writes:

> Hi --
>
> The sysadmins here at UT CS have built GCL 2.6.8pre from CVS as you
> suggested.  It's working great on 32-bit linux, but I've run into an
> issue for 64-bit linux.
>
> You can re-create the issue on a UT CS 64-bit linux machine as
> follows.
>
> Start up ACL2 built on GCL, as follows:
>
> /projects/acl2/v3-4-linux/fast-linux-gcl-saved_acl2
>
> Then issue these commands:
>
>   ; Just to slow down the output from the next form:
>   (trace$ rewrite)
>
>   ; ACL2 disables the debugger by default; this restores it:
>   (set-debugger-enable t)
>
>   ; This goes pretty fast but you'll have time to interrupt it:
>   (thm (equal (append (append x x) x) (append x x x)))
>
>   [Now quickly interrupt with control-c, and then :q from the break.
>    If the form above completes, just try it again.  Eventually I think
>    you'll see a Lisp "fatal error" or even a "Segmentation fault".]
>
> By the way, I built /projects/acl2/v3-4-linux/fast-linux-gcl as
> follows, on lhug-0 (a 64-bit linux machine):
>
> rm -f TAGS ; mv make-fast-gcl.log make-fast-gcl.old.log ; (time nice make 
> PREFIX=fast-linux-gcl- LISP=my-fast-gcl) >& make-fast-gcl.log&
>
> where "my-fast-gcl" is a script containing:
>
> #!/bin/sh
> /lusr/opt/gcl-2.6.8pre/bin/gcl -eval "(defparameter 
> user::*fast-acl2-gcl-build* t)" $*
>
> Also by the way, if you instead run the following on a 32-bit UT CS
> linux machine
>
> /projects/acl2/v3-4-linux/gcl-saved_acl2
>
> then you won't see the interrupt problem described above (or at least,
> I didn't, and I tried).
>
> Thanks --
> -- Matt
>
>
>
>

-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah




reply via email to

[Prev in Thread] Current Thread [Next in Thread]