I will most likely redo a lot of that code some time next week. As for this week I am out of town and can only do so much until next monday.
Ryan 'jphr' Neufeld --------------------------- visit me at hammerofcode.com On 19-Aug-08, at 9:08 AM, Vincent Verhoeven wrote: > On Mon, Aug 18, 2008 at 7:15 PM, Ryan Neufeld <[EMAIL PROTECTED]> > wrote: >> Strange that it is segfaulting on an IGObject::getName(). Looks like >> the exact place it fails is result.first->getName() in #2 , line 299 >> of colonize.cpp. Weirdest part is that result.first points to i- >>> first, and i->first is cast as a planet then asserted, so IMO it >> should fail at the assert and not after it; since i->first should >> be a >> valid planet IGO if it passed its assert. >> > > I believe result.first will still be NULL when numUnits == 0 for each > bid, which happens when (for example) I place a Colonization order > from a planet with only 1 army. > > You should also emphasize in the documentations that troops are moved > from a planet to another planet with a colonization order, and bids > have nothing to do with the reinforcement pool as I first assumed (and > I believe vi1985 also thinks that - so it's not just me). Or perhaps > this has changed during development or something? Anyway, I was a bit > confused. > > Also, general learning moment... If I upload a core file, shouldn't I > also upload the executable? Or can I assume that, when build on > another machine, gdb will correctly find the symbols? Anyway, I don't > think it's necessary in this case, but I still don't fully comprehend > core files I think. > Oh, another question on the same topic: if I have a core file from a > stripped executable and I have a non-stripped version, can I somehow > combine the symbols from the non-stripped version with the core file? > This happened to me with my X server crashes from tpclient-pywx: I > have a core file but it's from a stripped version. Is that useful in > any way, either to me, the Ubuntu X maintainers or the X developers? > > Iwanowitch > _______________________________________________ > tp-devel mailing list > [email protected] > http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
