I still get the same error with sbcl 2:2.0.6-2. I don't get an error (no matter which sbcl version) with
(with-state-monad
(with-input-from-string (in "1")
(run!
(lambda (s) (cons (read s) s))
in)))
instead of
(with-input-from-string (in "1")
(with-state-monad
(run!
(lambda (s) (cons (read s) s))
in)))
Am Monday, den 07/13/2020 um 12:19:42 PM +0200 schrieb Sébastien Villemot
<sebast...@debian.org>:
> Control: tags -1 + upstream moreinfo
>
> Dear Florine,
>
> Le mercredi 08 juillet 2020 à 21:24 +0000, florine forine a écrit :
> > Package: sbcl
> > Version: 2:2.0.5-1
> > Severity: normal
>
> > I describe actions that lead to a "Memory fault" in sbcl.
> > Same error happens with sbcl 2.0.6.59-e802114ba.
> > No error with clisp and abcl.
> >
> > * What led up to the situation?
> >
> > in sbcl repl:
> >
> > (ql:quickload "cl-monad-macros")
> > (in-package :cl-monad-macros)
> > (with-input-from-string (in "1")
> > (with-state-monad
> > (run!
> > (lambda (s) (cons (read in) in))
> > in)))
> >
> > * What was the outcome of this action?
> >
> > CORRUPTION WARNING in SBCL pid 31499(tid 0x7f9abea152c0):
> > Memory fault at 0x7faf (pc=0x5219f454 [code 0x5219f350+0x104 ID
> > 0x5933], fp=0x7f9abe77f5b8, sp=0x7f9abe77f5a0) tid 0x7f9abea152c0
> > The integrity of this image is possibly compromised.
> > Continuing with fingers crossed.
> >
> > debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread
> > #<THREAD "main thread" RUNNING {10009C8083}>:
> > Unhandled memory fault at #x7FAF.
>
> I can replicate this problem with sbcl 2:2.0.5-1, but not with sbcl
> 2:2.0.6-2.
>
> Can you confirm that the latest sbcl upload fixes it for you too?
>
> Best,
>
> --
> ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
> ⣾⠁⢠⠒⠀⣿⡁ Debian Developer
> ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
> ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
>
--
signature.asc
Description: PGP signature
