;;;; -*- coding: utf-8; fill-column: 78 -*-
+changes in sbcl-1.0.28 relative to 1.0.27:
+ * minor incompatible changes: echo-streams now propagate unread-char to the
+ underlying input stream, and no longer permit unreading more than one
+ character.
+ * improvement: on x86/x86-64 Lisp call frames now have the same layout as C
+ frames, allowing for instance more reliable backtraces.
+ * improvement: the debugger REPL can now reference lexical variables
+ by name directly for code compiled with (DEBUG 3).
+ * improvement: errors from malformed declarations now have better source
+ paths associated with them. (thanks to Tobias Rittweiler)
+ * optimization: faster local calls on x86/x86-64
+ * bug fix: some error messages for out-of-bound array indexes confused the
+ index and the bound. (thanks to Stas Boukarev)
+ * bug fix: pretty printing malformed DEFPACKAGE forms (thanks to Sidney
+ Markowitz)
+ * bug fix: running regressions tests in shells without OSTYPE set now works.
+ (reported by Harald Hanche-Olsen)
+ * bug fix: more robust static space exhaustion signalling from
+ MAKE-STATIC-VECTOR (thanks to Daniel Lowe)
+ * bug fix: (SETF DOCUMENTATION) for anonymous function now throws the
+ docstring away instead of storing it under names such as (LAMBDA (X)).
+ (reported by Leslie Polzer)
+ * bug fix: timers could go off in the wrong order, be delayed indefinitely
+ (thanks to Ole Arndt for the patch)
+ * bug fix: RESTART-FRAME and RETURN-FROM-FRAME stack corruption
+ * bug fix: the discriminating function for PRINT-OBJECT no longer preserves
+ potentially-invalid effective methods in its cache.
+ * bug fix: SB-INTROSPECT:FIND-DEFINITION-SOURCE now works with funcallable
+ instances as well (thanks to Paul Khuong)
+ * bug fix: using RUN-PROGRAM does not interfere with SB-POSIX:WAIT,
+ SB-POSIX:WAITPID and their C equivalents.
+ * bug fix: RUN-PROGRAM does not crash on Darwin when stressed.
+
+changes in sbcl-1.0.27 relative to 1.0.26:
+ * new port: support added for x86-64 OpenBSD. (thanks to Josh Elsasser)
+ * new port: support added for x86-64 Solaris. (thanks to Alex Viskovatoff)
+ * improvement: the system either recovers from stack exhaustion or dies
+ properly as opposed to leaving the user uncertain of whether the handler
+ trampled on some random memory next to the stack or having to rely on
+ --lose-on-corruption (which is still a good idea to use in production
+ because stack exhaustion can happen in signal handlers which will likely
+ lead to hangs.)
+ * bug fix: fix gc related interrupt handling bug on ppc (regression from
+ 1.0.25.37, reported by Harald Hanche-Olsen)
+ * bug fix: work around signal delivery bug in darwin (regression from
+ 1.0.25.44, reported by Sidney Markowitz)
+ * bug fix: fix ERROR leaking memory (reported by David Thompson)
+
changes in sbcl-1.0.26 relative to 1.0.25:
- * incompatible change: GC-OFF and GC-ON are removed, they were
+ * incompatible change: an interruption (be it a function passed to
+ INTERRUPT-THREAD or a timer function) runs in an environment where
+ interrupts can be enabled. The interruption can use
+ WITH-INTERRUPTS or WITHOUT-INTERRUPTS as it sees fit. Use
+ WITHOUT-INTERRUPTS to avoid nesting of interruptions and
+ potentially running out of stack. Keep in mind that in the absence
+ of WITHOUT-INTERRUPTS some potentially blocking operation such as
+ acquiring a lock can enable interrupts.
+ * incompatible change: GC-OFF and GC-ON are removed, as they were
always unsafe. Use WITHOUT-GCING instead.
* new feature: runtime option --disable-ldb
* new feature: runtime option --lose-on-corruption to die at the
memory, stack, alien stack, binding stack, encountering a memory
fault, etc. In the absence of --lose-on-corruption a warning is
printed to stderr.
+ * enhancement: detect binding stack exhaustion
+ * enhancement: detect alien stack exhaustion on x86/x86-64
+ * improvement: generally more stable and reliable interrupt handling
+ * improvement: there is a per thread interruption queue,
+ interruptions are executed in order of arrival
+ * improvement: a repeating timer reschedules itself when the it has
+ finished, but expiration times are spaced equally. If an
+ expiration time is in the past it will trigger after a short grace
+ period that may give a chance to other things to run.
* optimization: slightly faster gc on multithreaded builds
* optimization: faster WITHOUT-GCING
* bug fix: when JOIN-THREAD signals an error, do it when not holding
* bug fix: INTERRUPT-THREAD on a dying thread could produce memory
fault.
* bug fix: finalizers, gc hooks never run in a WITHOUT-INTERRUPTS
+ * bug fix: fix random memory faults related to interrupts on alpha
+ * bug fix: fix random memory faults related to interrupts on sparc
* bug fix: fix deadlocks related to starting threads
+ * bug fix: fix deadlines on locks on futex platforms
+ * bug fix: restore errno in signal handlers
+ * bug fix: fix deadlocks related to hash tables
+ * bug fix: fix deadlocks in pcl
changes in sbcl-1.0.25 relative to 1.0.24:
* incompatible change: SB-INTROSPECT:FUNCTION-ARGLIST is deprecated, to be
projects / sbcl.git / blobdiff