From: Stas B. <sta...@gm...> - 2017-09-11 10:39:23
|
Fixed in 4244f8fbee75937b477cda086d6e52ccafd19db5. Thanks. On Mon, Sep 11, 2017 at 12:35 PM, Eric Marsden <eri...@fr...> wrote: > Hi, > > This is on Linux/ARM64. > > > * (lisp-implementation-version) > "1.3.21.108-e3c05bb0b" > * (defun foo (a) > (declare (notinline values)) > (declare (optimize (debug 2))) > (max 1 > (handler-case > (values a a a a a a a a a a a a a)))) > FOO > * (foo 1) > CORRUPTION WARNING in SBCL pid 30936(tid 0xffff897cd410): > Memory fault at 0x28 (pc=0x1002bc2aa8, sp=(nil)) > 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 {1002B20003}>: > Unhandled memory fault at #x28. > Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. > restarts (invokable by number or by possibly-abbreviated name): > 0: [ABORT] Exit debugger, returning to top level. > ((FLET "FORM-FUN-4" :IN FOO)) > unknown location: using block start > source: (HANDLER-CASE (VALUES A A A A A A A A A A A ...)) > > -- > Eric Marsden > https://risk-engineering.org/ > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel -- With best regards, Stas. |