Daimrod writes:
> Stefan Reichör writes:
>
>> Because I have learned today where to look up a crash in stumpwm, I have
>> another crash that happens from time to time.
>>
>> When I open a file containing an umlaut (e.g. ö) in evince, the whole
>> stumpwm session dies with the following backtrace
Stefan Reichör writes:
> Because I have learned today where to look up a crash in stumpwm, I have
> another crash that happens from time to time.
>
> When I open a file containing an umlaut (e.g. ö) in evince, the whole
> stumpwm session dies with the following backtrace:
I put the following sni
Also, and important: signal handlers need to be added to stumpwm to
prevent encoding errors from crashing the whole window manager. This
means some thing will not work if stumpwm assumes UTF-8 encoding and
the filenames or X give back Latin-1 or similar, but it's better than
dying.
Vladimir
On Tu
Which Unix are you using, and what kind of language settings do you
have? One way to find out is to 'echo $LANG' in the console.
It looks like the file name is in ISO 8859-1/Latin-1 (0xF6 is o with
the umlaut). So there are two solutions: set the default encoding to
latin-1 for stumpwm (I don't kn
It looks like the backtrace gets cut off before reaching the actually
relevant part. I'm not sure off the top of my head how to control the
length of backtraces being printed - is there anything like that in
the error handling of stumpwm?
Vladimir
On Tue, Feb 28, 2012 at 9:15 AM, Stephen Balousek
Because I have learned today where to look up a crash in stumpwm, I have
another crash that happens from time to time.
When I open a file containing an umlaut (e.g. ö) in evince, the whole
stumpwm session dies with the following backtrace:
Caught '
CONVERT-STRING-FROM-BYTES: Invalid byte sequenc
Because I have learned today where to look up a crash in
Caught '
CONVERT-STRING-FROM-BYTES: Invalid byte sequence #xF6 #x72 #x2E #x70 in
CHARSET:UTF-8 conversion
' at the top level. Please report this.
<1/143> # 3
<2/139> #
[138] unwind-protect frame
- #
<3/132> #
- :TOP-LEVEL
- #
<4/128> #
-
Hi,
I am getting a strange, intermittent crash of StumpWM and I am looking
for pointers on how to resolve it, or possible workarounds.
The relevant information from ~/.xsession-errors is:
Caught 'The value -28580123 is not of type UNSIGNED-BYTE.' at the
top level. Please report this.
