Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cbpye]

I've already reported it using the MantisBT, but I'm posting it here for the sake of discussion.  Anyone know what could be causing this?

DF 31.17 on Slackware-current 64-bit
steps to reproduce: Start DF.  Gen World.  Crash.

Code: [Select]

bash-4.1$ ./df
Loading bindings from data/init/interface.txt
Resetting textures
./df: line 6:  3826 Segmentation fault      ./libs/Dwarf_Fortress $*
bash-4.1$ ./df
Loading bindings from data/init/interface.txt
Resetting textures
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_fill_insert
./df: line 6:  3850 Aborted                 ./libs/Dwarf_Fortress $*
bash-4.1$ ./df
Loading bindings from data/init/interface.txt
Resetting textures
./df: line 6:  3863 Segmentation fault      ./libs/Dwarf_Fortress $*
bash-4.1$


[woose1]

I'm no super computer genius, but it looks like stuff screws up right when the game tries to load the ASCII textures. Perhaps it's because of the tileset you're using?

This seems to be remarkably similar:
http://bioselement.com/2010/07/dwarf-fortress-0-31-10-on-fedora/
It's on linux, and it deals with a library error.
I wish I knew more about computers so I could help you... 

[cbpye]

The "Resetting Textures" bit has always been there, even in previous versions where I didn't have this issue.

[macdonellba]

I've already reported it using the MantisBT, but I'm posting it here for the sake of discussion.  Anyone know what could be causing this?

DF 31.17 on Slackware-current 64-bit
steps to reproduce: Start DF.  Gen World.  Crash.

Code: [Select]

bash-4.1$ ./df
bash-4.1$ ./df
Loading bindings from data/init/interface.txt
Resetting textures
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_fill_insert
./df: line 6:  3850 Aborted                 ./libs/Dwarf_Fortress $*


AFAIK that length error would be because a vector is being resized above the maximum implementation-defined size, as reported by the max_size member function. As for how a vector could be hitting those limits in practice, I honestly have no idea.