Comment # 4
on bug 9814
from Guy Harris
This might be Windows-specific - see bug 6089 and bug 6932.
The actual crash appears to be a bug in GTK+, wherein, on Windows, it crashes
when copying some non-ASCII strings - possibly if they contain invalid UTF-8
sequences.
We shouldn't be displaying invalid UTF-8 sequences. We're working on changing
string handling in dissectors so that invalid UTF-8 sequences don't show up in
dissections.
However, if, when we truncate strings in the packet display, we don't truncate
them on UTF-8 sequence boundaries, that would *also* introduce UTF-8 sequences
into the display. The string appears to be a sequence of Euro symbols, but it
displays on my Mac, at least, with a X-ed out rectangle at the end, so I
suspect we're *not* truncating strings on UTF-8 sequence boundaries.
You are receiving this mail because:
- You are watching all bug changes.