libera/#commonlisp - IRC Chatlog
Search
1:19:48
atgreen
_death, hayley .. reverting SBCL from 2.2.7 to 2.2.6 solved my corruption error from earlier today
1:27:04
hayley
I'm too busy today to look through the cl-postgres code, but it is still possible that it is modifying literals in a way that isn't allowed in Common Lisp, and it's caught by SBCL 2.2.7 now.
1:29:04
hayley
...after a quick glance that doesn't seem likely, but there is a (optimise (safety 0)) declaration that you could remove.
1:46:36
hayley
(setf (aref "blab" 2) #\u) is undefined behaviour. After SAVE-LISP-AND-DIE, SBCL 2.2.7 would put that string in read-only memory, so trying to write to the string would cause a memory fault.
1:47:02
hayley
But I don't think that's the issue; the use of (safety 0) in that function causing a memory fault is more concerning to me now.
3:17:56
aeth
easy bonus points to score: submit PRs to remove all (safety 0) except when the (safety 0) actually has a purpose (basically, to remove bounds checks) and even then you can probably move it to a tightly bound LOCALLY (instead of the typical function scope) to limit the chance of bugs surfacing there
9:14:16
_death
atgreen: but did you run your program with the unsafety declarations removed? then it might've exposed a bug