Follow-up Comment #6, bug #16618 (project wesnoth):
Gunter, please checks the changes made to Revision #46654.
It should fix the TODO issue and maybe even help with wesnothd crashing.
Any more information you have regarding these bugs or how to reproduce them
is welcomed.
Later tonight I'll
Follow-up Comment #5, bug #16618 (project wesnoth):
There is no way to reproduce, though you got the backtraces to go by. Short
version how Soliton summed it up:
[14:33:31] Soliton i mean there are backtraces in the report that point to
exact source lines which throw TODO notes...
[14:34:41]
Follow-up Comment #2, bug #16618 (project wesnoth):
As mentioned I'm not sure if the build was uptodate enough but as you can see
from the mentioned revision bug #16502 was already fixed in it.
___
Reply to this item at:
Follow-up Comment #3, bug #16618 (project wesnoth):
another crash, probably a different problem so maybe we need to open another
report later. Tell me if you need the bt of other threads etc.
Last log message: norbert has left game: IPS's game (4). (socket: 14)
pure virtual method called
Follow-up Comment #4, bug #16618 (project wesnoth):
I would like to know how to reproduce these bugs.
The original post seems to be a duplicate from bug #16502.
___
Reply to this item at:
http://gna.org/bugs/?16618
URL:
http://gna.org/bugs/?16618
Summary: wesnothd: client login issues
Project: Battle for Wesnoth
Submitted by: soliton
Submitted on: Thursday 09/02/2010 at 21:15
Category: Bug
Severity: 4 - Important
Follow-up Comment #1, bug #16618 (project wesnoth):
I fixed a very similar bug in Bug #16502.
Are you sure you have the latest revision of the code?
___
Reply to this item at:
http://gna.org/bugs/?16618
