Follow-up Comment #1, bug #16393 (project wesnoth):
I confirm this bug.
My last changes to the codebase were to modify the connection procedure to
only inform the first result of the connection attempt. So maybe the bug
comes from those changes.
However I reverted those changes and the bug still occurs. Is it possible
that this is related to WML itself?
The error is:
"Invalid WML received: did not find quotes around attribute"
And this was typical when receiving badly garbled up network packets... but I
don't see where my code changes screwed up. I actually run a few simple tests
before commiting something.
I'm compiling the debug version ATM to check the problem.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?16393>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
