starting a swank server segfaults when core files are used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Slime |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
a memory fault reliably happens when a swank server is started when sbcl was loaded from a previously saved core file, which had swank initialized.
Nikodemus identified the issue:
I'm thinking you're holding on to a live stream from a previous invocation, and then trying to write to the mmap'ed stream buffer which doesn't exist anymore.
Looking at SIMPLE-
a possible fix:
(in-package :swank)
(defun after-saved-
(setf *log-output* nil)
(init-
#+sbcl(pushnew 'after-
Changed in sbcl: | |
status: | New → Invalid |
summary: |
- reproducible memory fault from SB-IMPL::OUTPUT-BYTES/UTF-8 + starting a swank server segfaults when core files are used |
Changed in slime: | |
status: | New → Fix Committed |
Changed in slime: | |
status: | Fix Committed → Fix Released |
Is the fault address deterministic?
I'm OK with the tarball.