[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] Re: bug in read-byte
From: |
Camm Maguire |
Subject: |
[Gcl-devel] Re: bug in read-byte |
Date: |
15 Apr 2006 21:08:31 -0400 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Greetings! This is the same static issue as in the gabriel fft -- the
static linking sequence we pass to ld is not writing the C symbols
occasionally written by the GCL compiler (cos, feof, etc) in a manner
which we can (yet) parse to find their addresses in
bfd_build_symbol_table. A work around for now should be (si::remprop
'read-byte 'compiler::co1).
Please let me know if problems persist.
Take care,
Robert Boyer <address@hidden> writes:
> Some systems just crashed on me, so I'm not 100% sure the
> message below went out to you.
>
> I'm betting it did, so please forgive this repeat.
>
> There is a bug in the compilation of 'read-byte' which
> causes it to return nonsense or even segmentation violation
> on end of file.
>
> Bob
>
> -------------------------------------------------------------------------------
>
>
> % cat fap.lisp
> a% xg
> GCL (GNU Common Lisp) 2.7.0 ANSI Apr 14 2006 16:04:17
> Source License: LGPL(gcl,gmp,pargcl), GPL(unexec,bfd)
> Binary License: GPL due to GPL'ed components: (BFD UNEXEC)
> Modifications of this banner must retain notice of a compatible license
> Dedicated to the memory of W. Schelter
>
> Use (help) to get some basic information on how to use GCL.
> Temporary directory for compiler files set to /tmp/
>
> >(defun foo (x) (read-byte x nil nil))
>
> FOO
>
> >(compile 'foo)
>
> ;; Compiling /tmp/gazonk_6750_0.lsp.
> ;; End of Pass 1.
> ;; End of Pass 2.
> ;; OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3,
> (Debug quality ignored)
> ;; Finished compiling /tmp/gazonk_6750_0.o.
> Loading /tmp/gazonk_6750_0.o
> start address -T 0xab455c8 Finished loading /tmp/gazonk_6750_0.o
> #<compiled-function FOO>
> NIL
> NIL
>
> >(setq *s* (open "fap.lisp"))
>
> #<input stream "fap.lisp">
>
> >(foo *s*)
>
> 97
>
> >(foo *s*)
> Segmentation violation: c stack ok:signalling error
> Error in EVAL [or a callee]: Caught fatal error [memory may be damaged]:
> Segmentation violation.
>
> Fast links are on: do (si::use-fast-links nil) for debugging
> Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. Type :H for Help.
> 1 (Continue) Return to top level.
> dbl:>>
>
>
>
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gcl-devel] Re: bug in read-byte,
Camm Maguire <=