Can't run latest Git celeron master (Solved)

[redcrab]

latest git celeron master wont run (minetestserver)

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

04:06:28: INFO[main]: Initializing new map.
04:06:28: INFO[main]: ServerMap: Saving whole map, this can take time.
04:06:28: INFO[main]: ServerMap::saveMapMeta(): seed=5165442295542071705
04:06:28: INFO[main]: ServerMap: Written: 0 sector metadata files, 0 block files, 0 blocks in memory.
04:06:28: INFO[main]: ServerMap: Blocks modified by:
04:06:28: INFO[main]: scriptapi_add_environment
04:06:28: INFO[main]: EnvRef created
04:06:28: ERROR[main]: WARNING: myrand_range: max-min > MYRAND_MAX

In thread b739b6d0:
/home/edevaux/Projects/Minetest-staging/src/utility.cpp:165: int myrand_range(int, int): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD b739b6d0:
#0  int main(int, char**)
(Leftover data: #1  virtual void ServerMap::save(ModifiedState))
(Leftover data: #2  void ServerMap::saveMapMeta())


May be a my "git pull" takes a too early code ;)

[Hackeridze]

http://pastebin.com/qcsb3y6q
Same problem.

[celeron55]

It is a bug, kind of; just a minute, I'll fix it.

EDIT: Replaced whole post

[celeron55]

Now it is fixed.

Make sure to note that the cause was some mod that is setting a very high or somehow otherwise strange ABM interval.

This means the ABM might not trigger at all anymore. The ABM interval was incorrectly handled before some commit *after* snapshot 0.4.dev-20120102-1.

I am not sure about the specifics on how they worked wrongly, but I know that at least saplings grew up way too quickly, seeming like the chance value was just ignored and it triggered on every interval regardless of it being set to 50.

[redcrab]

Now it is fixed.

Make sure to note that the cause was some mod that is setting a very high or somehow otherwise strange ABM interval.

This means the ABM might not trigger at all anymore. The ABM interval was incorrectly handled before some commit *after* snapshot 0.4.dev-20120102-1.

I am not sure about the specifics on how they worked wrongly, but I know that at least saplings grew up way too quickly, seeming like the chance value was just ignored and it triggered on every interval regardless of it being set to 50.

Thanks,

I confirm that your fix allows me to run the server.
regards