[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [STUMP] Encoding error (SBCL)
From: |
Julian Stecklina |
Subject: |
Re: [STUMP] Encoding error (SBCL) |
Date: |
Sat, 26 Dec 2009 16:28:59 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
"Tobias C. Rittweiler" <address@hidden> writes:
> Julian Stecklina <address@hidden> writes:
>
>> Hello,
>>
>> recently I started getting these:
>>
>> ; compiling file "/home/julian/src/lisp/stumpwm/version.lisp" (written 21
>> DEC 2009 09:18:14 PM):
>> ; compiling (IN-PACKAGE :STUMPWM)
>> ; compiling (EXPORT (QUOTE #))
>> debugger invoked on a SB-INT:C-STRING-DECODING-ERROR in thread #<THREAD
>> "initial thread" RUNNING {A9AA8E1}>:
>> c-string decoding error (:external-format :UTF-8):
>> the octet sequence 2 cannot be decoded.
>>
>> This happens with SBCL 1.0.31 and 1.0.33 (I did not try any other
>> versions so far). If you remove the call to run-shell-command in
>> version.lisp, it happens when stumpwm calls xdpyinfo on startup. Any
>> hints?
>
> What 1.0.33.x exactly? Perhaps it's this
>
> https://bugs.launchpad.net/sbcl/+bug/460455
>
> which was fixed in 1.0.33.21.
It seems to be this bug. Thanks for the info!
Regards,
--
Julian Stecklina
The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge