OK, now it's crashing with an ****ertion. March 27, 2010, 07:56:47 am Running my patched and compiled simutrans-experimental, crashes during map creation with this ****ertion:simutrans-experimental: simfab.cc:289: fabrik_t::~fabrik_t(): ****ertion `plan' failed.(Why is it running a factory *destructor* during map creation?)If I put in a settings.xml file it instead segfaults. Quote Selected
Re: OK, now it's crashing with an ****ertion. Reply #1 – March 27, 2010, 09:29:37 am Which "map creation" ? The one directly on startup before rolling credits screen, or the one you start from new world dialogue? In the latter case the old map must be removed Quote Selected
Re: OK, now it's crashing with an ****ertion. Reply #2 – March 27, 2010, 09:40:28 am Quote from: VS – on March 27, 2010, 09:29:37 amWhich "map creation" ? The one directly on startup before rolling credits screen, or the one you start from new world dialogue? In the latter case the old map must be removed Ah-HA. It's the one you start from new world dialogue. So it's probably dying dismantling the old map.... Quote Selected
Re: OK, now it's crashing with an ****ertion. Reply #3 – March 27, 2010, 09:54:27 am OK, I can generate a *different* crash-to-****ertion bug. If I go into public service mode (on the initial map) and start deleting factories, eventually I'll get this crash:sim: simfab.cc:295: fabrik_t::~fabrik_t(): ****ertion `f' failed.It's not completely predictable; I appear to be able to delete some before getting it.Deleting the Walmington-on-Sea Forest/Sawmill seems to be the most reliable way of prodicing *this* crash.The *GOOD* news is, if I delete the demo.sve file from Pak128.Britain.Ex 0.5.before starting up, then everything works. (So far.) So it's a save file compatibility issue.And now I can actually test the game. Quote Selected Last Edit: March 27, 2010, 10:01:26 am by neroden
Re: OK, now it's crashing with an ****ertion. Reply #4 – March 28, 2010, 06:00:49 pm Thank you very much indeed for your reports - much appreciated. The problem appears to be that it is attempting to delete fields that don't exist. In a version compiled with the -NDEBUG switch on, the ****ertion will simply be p****ed by, which is what should be the case for the release version. I presume that you compiled your own in Linux without the -NDEBUG switch? Quote Selected
Re: OK, now it's crashing with an ****ertion. Reply #5 – March 29, 2010, 11:13:58 pm Quote from: jamespetts – on March 28, 2010, 06:00:49 pmThank you very much indeed for your reports - much appreciated. The problem appears to be that it is attempting to delete fields that don't exist. In a version compiled with the -NDEBUG switch on, the ****ertion will simply be p****ed by, which is what should be the case for the release version. I presume that you compiled your own in Linux without the -NDEBUG switch?Yes. I had to do that to get a working version, as documented in other bug threads. Quote Selected