libera/#sbcl - IRC Chatlog
Search
8:00:53
semarie
even if sigaltstack failed, it just mean that the "normal" stack is enough for the work
8:01:59
semarie
regarding "yes, this fixes things for me", it is the case. but as I said in my mail, it could be tricky to run in a case where effectively the alt-stack being used
8:02:37
semarie
the memory segment used for sigaltstack(2) is normally only used for signals delivered context
11:08:00
luis
Got a strange #<error printing a FIXNUM: #<TYPE-ERROR expected-type: REAL datum: (error printing condition)>>. Any hints on how that can happen? https://plaster.tymoon.eu/view/3827
11:23:19
scymtym
the expected type looks like things that would be acceptable to FORMAT, the actual value seems to be an error condition. my guess would be a condition with :report (lambda (condition stream) ...) or :report (lambda (stream condition) ...) whichever is the wrong one
11:30:42
luis
karlosz, scymtym: why would that show up in the NAME variable (frame #1, line 11) though?
11:32:36
scymtym
maybe the pprint dispatch table or the debugger stream are broken? printing a FIXNUM shouldn't fail otherwise
11:57:35
luis
Hmm, that value is being printed with (let ((sb-ext:*suppress-print-errors* t)) (format stream "~a = ~s~%" (sb-di:debug-var-symbol var) (sb-di:debug-var-value var frame))), so I guess that's why it looks like a condition.
11:58:40
luis
yes, normal 2.0.2 brokenness :) (or more likely, or backtrace printing code is broken)
12:00:32
Krystof
so that seems to be saying that parse-native-namestring's first argument is a fixnum
12:01:30
Krystof
it wanted to print you a fixnum as the first argument, but printing it failed, even though a fixnum is a real