Odd characters showing up in output screen

Posted by Krenath on Sat 22 Feb 2003 05:51 PM — 5 posts, 19,490 views.

USA #0
Periodically, I see odd characters in the output screen replacing the text that should have been there. Fairly often, it happens when I type something that's sent to the world.

Nobody else sees the occ characters but be, so it's in what gets displayed on my screen, not what's sent to or from the MUSH.

Most often, the characters are 'http' but occasionally are high ascii characters. So far, all occurrances have been four characters long.

Most recent example:

sent to world: my cablemodem
received: m[ÁpÉblemodem
Amended on Sat 22 Feb 2003 05:53 PM by Krenath
Australia Forum Administrator #1
Quote:

Nobody else sees the occ characters but be


Seems to be happening on the forum as well! :)

Strange, is this happening to anyone else? Sounds like a MUD outputting problem, or transmission error. Try doing a packet debug if it happens often enough that you can reproduce it inside 5 minutes.
USA #2
Here's a packet where the problem showed up.
The name of the player speaking is supposed to be "Cerekk" but four characters in the middle of his name were changed to garbage.

Incoming packet: 3995 (78 bytes)

.[36mC....k says   1b 5b 33 36 6d 43 00 00 ac 13 6b 20 73 61 79 73
, ".[1;37mheh. o   2c 20 22 1b 5b 31 3b 33 37 6d 68 65 68 2e 20 6f
ne setr, drop 20   6e 65 20 73 65 74 72 2c 20 64 72 6f 70 20 32 30
0 function calls   30 20 66 75 6e 63 74 69 6f 6e 20 63 61 6c 6c 73
.[0m.[36m".[0m     1b 5b 30 6d 1b 5b 33 36 6d 22 1b 5b 30 6d

Amended on Mon 24 Feb 2003 03:36 AM by Krenath
Australia Forum Administrator #3
The packet debug is written out very early in MUSHclient's packet processing (right after decompression, if applicable) so if the junk is there it is very likely it arrived like that. I suggest the server has a bug where it is corrupting its output. Try a different client. I doubt MUSHclient is doing it.
Australia Forum Administrator #4
A few versions back an obscure bug was fixed that might be related to this. A buffer was being shared between worlds, that might have accounted for this behaviour.