[Gcl-devel] Re: still a problem with interrupts in 64-bit GCL

[Matt Kaufmann]

Excellent -- thanks, Dave.

-- Matt
   Date: Tue, 03 Mar 2009 09:07:45 -0600
   From: "David A. Kotz" <address@hidden>
   CC: address@hidden, address@hidden, address@hidden

   I'll rebuild it and put it in /lusr/opt/gcl-2.6.8.pre-debug on the 64bit 
   machines.

   - dave


   Matt Kaufmann wrote:
   > Hi, Dave --
   > 
   > Is the debug version still sitting around somewhere, or can you build
   > one in a different location from the same sources?  Then I could try
   > to get the bug to occur with the debug version.
   > 
   > That's about the only contribution I know how to make....
   > 
   > Thanks --
   > -- Matt
   >    Date: Tue, 03 Mar 2009 09:02:01 -0600
   >    From: "David A. Kotz" <address@hidden>
   >    CC: address@hidden, address@hidden, address@hidden
   > 
   >    That's strange.  All I did to build it this time was to remove the 
debug 
   >    line from my configure script.  The updated 32bit version was rdisted 
   >    around in the wee hours of this morning, but the new 64bit version was 
   >    in place at the time I sent email about it.
   > 
   >    __________________________
   > 
   >    #!/lusr/bin/bash
   >    ./configure --prefix=/lusr/opt/gcl-2.6.8pre \
   >       --disable-statsysbfd --enable-locbfd \
   >       --enable-ihssize=2097110             \
   >       --enable-vssize=2097110              \
   >       --enable-maxpage=524288              \
   >       --enable-holediv=100                 
   > 
   >    ___________________________
   > 
   > 
   >    Let me know what I can do to help.
   > 
   >    - dave
   > 
   > 
   >    Matt Kaufmann wrote:
   >    > Hi --
   >    > 
   >    > I really appreciate the work you've done (Camm and Dave), but
   >    > unfortunately we seem to be back where we started.  I've included my
   >    > email with the original issue below, so that you can re-create the
   >    > problem.  (I've redone the steps listed below, in the locations
   >    > specified.)
   >    > 
   >    > By the way, I'm still not seeing the problem with 32-bit GCL; just
   >    > 64-bit.
   >    > 
   >    > Thanks --
   >    > -- Matt
   >    >    Date: 20 Feb 2009 08:23:17 -0600
   >    >    From: Matt Kaufmann <address@hidden>
   >    >    CC: address@hidden, gripe
   >    > 
   >    >    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