libera/#commonlisp - IRC Chatlog
Search
2:25:53
jcowan
Guile has (), #f, and #nil so that it can handle both the Elisp/CL system and the Scheme system. Specifically, #nil and #f are both false, and #nil and () are both empty lists.
2:26:52
jcowan
So you shouldn't make inquiries like (eq x nil), instead you should use (not x) or (null x).
13:19:33
asarch
Why could you get this error in SBCL?: "The integrity of this image is possibly compromised."
13:25:26
asarch
This is the log when I ran my web app for the first time: https://pastebin.com/8wAKuWGR
13:26:24
Bike
this still doesn't mention what actually happened before the corruption warning, does it?
13:51:19
aeth
asarch: "the integrity of the image" is either a CFFI or (safety 0) or similar bug, probably out of bounds, maybe something like use-after-free... perhaps even a dynamic-extent that escaped the scope. Something dangerous happened, poorly.
13:52:22
aeth
It's basically something that would have resulted in "Segmentation fault" if C or C++, but instead the image continues running, but probably shouldn't because it's probably still broken.
13:54:02
aeth
And if you're one of those people who has an emacs server with SLIME running 24/7 then it's probably really annoying.
13:54:26
aeth
Since one Lisp process could run multiple programs, perhaps even the entire DE (see e.g. stumpwm) and needs restarting
13:54:53
aeth
But if you're running it from the shell, no big deal. Just find the bug with CFFI, (safety 0), dynamic-extent, or similar
13:55:20
aeth
(Really, you shouldn't use (safety 0) at all except perhaps inside a LOCALLY to very, very clearly limit the possible damage)
14:01:36
asarch
I thought it was IRONCLAD: "[2022-08-18 09:01:08 [WARNING]] Warning while processing connection: redefining IRONCLAD:WITH-DECRYPTING-STREAM in DEFMACRO"
14:12:58
aeth
libraries will also e.g. inline at the wrong place so they don't actually get inlined etc etc