I encoundered an access violation...
Consistently, or just once? With any particular galaxy setup options or with any? Does it happen with the v0.3.13 release as well? Immediately after starting a new single-player game when running the program, or only after resigning a game and starting another, or only when starting a multiplayer game?
For some reason the debugger don't want to show me the contents of buildings (undeclared symbol).
Add debug output to console or log file. To do this, iterate through whatever container you're interested in and output something relevant about its contents:
for (std::map<A, B>::const_iterator it = container.begin() it != container.end(); ++it)
std::cout << "info: " << it->second->Name() << " or some such...";
It seems like the first passed parameter to StoreTargetsAndCausesOfEffectsGroups (effects_groups) is invalid. The debugger shows '[...]()' for its value and I've no idea what that's supposed to mean. An empty std::vector would appear as ().
Is there a little + button? If there's a bunch of stuff in a container, the MSVC debugger sometimes lets you expand the container. If it's gotted confused and can't evaluate the container properly, it sometimes says it has 500000 entries in it, or somesuch, though.
Maybe it has to do with a recent change in buildings.txt, where the effects for BLD_SHIPYARD_BASE and BLD_SHIPYARD_ORBITAL_DRYDOCK have been removed, but even when I reverted this change the exception was still thrown.
It's more likely related to the one before that: http://freeorion.svn.sourceforge.net/vi ... ision=3041
in which building effects were made optional.
Can someone reproduce this error?
Possibly, if you can be more specific (see above).
btw: is there an easier way to attach the debugger to the server before universe generation than hosting a multiplayergame and then joining with a second local client?
When on the single player galaxy setup screen, the server has already been launched and can be connected with the MSVS debugger.
Somewhere I read about a --force-external-server option, but it seems as if it has been removed.
freeorion -h wrote:
Force the client not to start a server, even when hosting a game on
localhost, playing single player, etc.