Skip to content

Instantly share code, notes, and snippets.

@3b

3b/foo.lisp Secret

Created April 24, 2020 22:53
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save 3b/2bc8911f30ad6b0820d608205012e4f1 to your computer and use it in GitHub Desktop.
Save 3b/2bc8911f30ad6b0820d608205012e4f1 to your computer and use it in GitHub Desktop.
(with-open-file (f "/tmp/foo.lisp" :direction :input
:element-type '(unsigned-byte 8))
(read-byte f)
(let ((buf (make-array 0 :element-type '(unsigned-byte 8))))
(read-sequence buf f)))
/tmp/acl10.1express$ ./alisp
International Allegro CL Free Express Edition
10.1 [32-bit Linux (x86)] (Jan 9, 2019 10:41)
Copyright (C) 1985-2019, Franz Inc., Oakland, CA, USA. All Rights Reserved.
This development copy of Allegro CL is licensed to:
Allegro CL 10.1 Express user
;; Optimization settings: safety 1, space 1, speed 1, debug 2.
;; For a complete description of all compiler switches given the
;; current optimization settings evaluate (EXPLAIN-COMPILER-SETTINGS).
CL-USER(1): (load "/tmp/foo.lisp")
; Loading /tmp/foo.lisp
; Autoloading for EXCL::GRAY-OPEN:
; Fast loading from bundle code/streamc.fasl.
; Fast loading from bundle code/efft-utf8-base.fasl.
; Fast loading from bundle code/efft-void.fasl.
; Fast loading from bundle code/efft-latin1-base.fasl.
Allegro CL(pid 27531): System Error (gsgc) Scavenger invoked itself recursively.
The internal data structures in the running Lisp image have been
corrupted and execution cannot continue. Check all foreign functions
and any Lisp code that was compiled with high speed and/or low safety,
as these are two common sources of this failure. If you cannot find
anything incorrect in your code you should contact technical support
for Allegro Common Lisp, and we will try to help determine whether
this is a coding error or an internal bug.
A core file can be produced at this time. Core files may or may not
be useful in diagnosing an error of this type and are often not useful.
See doc/introduction.htm#core-dumps-2 for more details.
Would you like to dump core before exiting(y or n)?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment