Print Page - Segmentation fault (core dumped) on starting

Title: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 10:19:44 am

Dear openxcom-people,

I'm on Xubuntu 15.10 (32-bit), and I got my copy of openxcom as well as the fixed libyaml-cpp from this launchpad: https://launchpad.net/~knapsu/+archive/ubuntu/openxcom (https://launchpad.net/~knapsu/+archive/ubuntu/openxcom). I've also installed the other dependencies mentioned in the installation instructions, as well as timidity (since I saw that someone else needed that). Then:

1. I got my copy of XCOM: UFO DEFENCE from Steam yesterday, and I downloaded and extracted your universal patch in the XCOM/ folder, replacing files as necessary. (Before this I tarballed a backup copy of the folder just in case).

2. I then first tried copying all the mentioned folders individually to the data folder ( /usr/share/openxcom in my case, not /usr/local/share/openxcom as in your example - but alas, starting the program with openxcom -data "/usr/share/openxcom/data" still yields segfault), keeping permissions, no go, then I copied the entire contents of the XCOM/ folder, still segfault, then I chmod 777 -R the entire /usr/share/openxcom/ folder just to make sure there where no permission problems, still segfault.

I seem to get no logfile (~/.local/share/openxcom/ is empty). What should I do now? I read about x-piratez on Rock Paper Shotgun and I would like to try it out.

Thanks!

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 11:01:05 am

Hi,

if you are talking specifically about X-PirateZ, then you need to follow the X-PirateZ installation instructions.
They are different from just OpenXcom installation instructions.

1. download the game, link here: https://openxcom.org/forum/index.php/topic,3626.0.html
2. extract anywhere
3. copy the Steam data into the folder: "<X-pirateZ folder>/UFO" (please note copying them anywhere else will NOT work)
4. if you're on windows, just run the game (OpenXcomExPlus29.exe)

4a. if you're on Linux, you need to install pre-requisites too (see here: https://openxcom.org/forum/index.php/topic,4187.msg65619.html#msg65619)

Code: [Select]

sudo apt-get install libsdl1.2-dev libsdl-mixer1.2-dev libsdl-gfx1.2-dev libsdl-image1.2-dev libyaml-cpp-dev4b. if you have the newest version 0.99, try running the executable provided in the package (OpenXcomExPlusElf), if not then you can either build your own executable (see below) or download it from my thread (see below)

Important:
X-PirateZ runs on custom executable, it comes either bundled with the game (v0.99), or in this thread: https://openxcom.org/forum/index.php/topic,4187.0.html or you can compile it on your own (directions in the same thread)

Regards,
Meridian

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 01:11:00 pm

Hello!

Thats nice! Well, I fiddled around a bit. First I tried you instructions above, but executing your modified executable yields:

./OpenXcomExPlusElf: symbol lookup error: ./OpenXcomExPlusElf: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarE

So then I tried it according to the Piratez installation instructions, ie after purging my openxcom i installed openxcom-extended, then copied user/ from piratez to /usr/share/openxcom/ as well as the UFO-folder with GEODATA etc. from the vanilla game to the same folder. NOW, starting openxcom brings me to the setup screen (hot damn that's some awesome music and graphics), where I set all the advanced options according to the piratez README as well as tweaked the resolution and filters and stuff nicely, then went to the MODS tab and selected x-piratez, enabled some of the mods (not the xutils one, I heard thats no good for linux?), but alas when I say AYE to start a new game on the easiest difficulty, crash:

libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
libpng warning: Out of place iCCP chunk
Segmentation fault (core dumped)

In this thread (https://openxcom.org/forum/index.php?topic=3010.5) I found something similar, but I cannot figure out how it relates to my problem. Any ideas?

Thank you for your speedy answer!

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 01:59:16 pm

Quote from: buenaventura on June 10, 2016, 01:11:00 pm

So then I tried it according to the Piratez installation instructions, ie after purging my openxcom i installed openxcom-extended, then copied user/ from piratez to /usr/share/openxcom/ as well as the UFO-folder with GEODATA etc. from the vanilla game to the same folder.

Where did you find these instructions?
I am not aware of anything like this...

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 02:07:08 pm

Quote from: Meridian on June 10, 2016, 01:59:16 pm

Where did you find these instructions?
I am not aware of anything like this...

Oh? I found them in the archive, OpenXcom_XPiratez/XPiratez readme/OXCE_Readme.txt and XPiratez_readme.txt .

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 02:08:38 pm

Quote from: buenaventura on June 10, 2016, 02:07:08 pm

Oh? I found them in the archive, OpenXcom_XPiratez/XPiratez readme/OXCE_Readme.txt and XPiratez_readme.txt .

Oh, I see it now, in "XPiratez_readme.txt"... well, this is unfortunately too old/obsolete, X-PirateZ runs on OpenXcom-Extended-Plus now... the OpenXcom-Extended, which you have probably downloaded from mod portal will not work correctly. I'm afraid you'll need to follow my instructions above... and if the precompiled executable doesn't work for you, try talking to people who are compiling it themselves: Yankes, Arthanor, etc. Hopefully one of them will be able to respond here too.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 02:44:15 pm

Quote from: Meridian on June 10, 2016, 02:08:38 pm

Oh, I see it now, in "XPiratez_readme.txt"... well, this is unfortunately too old/obsolete, X-PirateZ runs on OpenXcom-Extended-Plus now... the OpenXcom-Extended, which you have probably downloaded from mod portal will not work correctly. I'm afraid you'll need to follow my instructions above... and if the precompiled executable doesn't work for you, try talking to people who are compiling it themselves: Yankes, Arthanor, etc. Hopefully one of them will be able to respond here too.

Right, well, I will do my best. I tried running the .exe in Wine (why not), it opens the first loadingscreen, but gets stuck at "Loading openxcom-extended-plus 2016...." or something like it. Too bad!

I also tried your modified linux executable as said, with the above cryptic error. Any ideas on that? Otherwise...

Hey, Yankes, Arthanor! (should I start a new thread somewhere?)

I am trying to compile myself now, according to these instructions: https://www.ufopaedia.org/index.php?title=Compiling_with_CMake_%28OpenXcom%29#End-to-end_example (https://www.ufopaedia.org/index.php?title=Compiling_with_CMake_%28OpenXcom%29#End-to-end_example)
First I hade the wrong version of libyaml-cpp, I got the right one from this launchpad: https://launchpad.net/~winterheart/+archive/ubuntu/openxcom (https://launchpad.net/~winterheart/+archive/ubuntu/openxcom)
Now cmake does fine, but make gives me this:

Scanning dependencies of target openxcom
[ 0%] [ 0%] [ 0%] [ 0%] [ 0%] [ 1%] [ 1%] [ 2%] [ 3%] [ 3%] Building CXX object src/CMakeFiles/openxcom.dir/main.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/CraftArmorState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/lodepng.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/CraftEquipmentState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BaseView.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/BuildFacilitiesState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/CraftSoldiersState.cpp.o
Building CXX object src/CMakeFiles/openxcom.dir/Basescape/CraftInfoState.cpp.o
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/BaseInfoState.cpp:24:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:100: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BaseInfoState.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/CraftArmorState.cpp:21:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:192: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/CraftArmorState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/CraftArmorState.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Engine/OptionInfo.h:20,
from /home/simon/games/openxcom_sandbox/openxcom/src/Engine/Options.h:23,
from /home/simon/games/openxcom_sandbox/openxcom/src/main.cpp:24:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/BasescapeState.cpp:21:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:77: recipe for target 'src/CMakeFiles/openxcom.dir/main.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/main.cpp.o] Error 1
src/CMakeFiles/openxcom.dir/build.make:146: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BasescapeState.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/CraftSoldiersState.cpp:23:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:261: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/CraftSoldiersState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/CraftSoldiersState.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Savegame/Target.h:22,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Savegame/Base.h:20,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/BaseView.cpp:25:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:123: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BaseView.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BaseView.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/BuildFacilitiesState.cpp:21:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:169: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/BuildFacilitiesState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/BuildFacilitiesState.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/CraftInfoState.cpp:23:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:238: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/CraftInfoState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/CraftInfoState.cpp.o] Error 1
In file included from /usr/include/yaml-cpp/node/node.h:17:0,
from /usr/include/yaml-cpp/yaml.h:16,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/../Mod/Mod.h:24,
from /home/simon/games/openxcom_sandbox/openxcom/src/Basescape/CraftEquipmentState.cpp:27:
/usr/include/yaml-cpp/node/ptr.h:11:32: fatal error: boost/shared_ptr.hpp: No such file or directory
compilation terminated.
src/CMakeFiles/openxcom.dir/build.make:215: recipe for target 'src/CMakeFiles/openxcom.dir/Basescape/CraftEquipmentState.cpp.o' failed
make[2]: *** [src/CMakeFiles/openxcom.dir/Basescape/CraftEquipmentState.cpp.o] Error 1
CMakeFiles/Makefile2:90: recipe for target 'src/CMakeFiles/openxcom.dir/all' failed
make[1]: *** [src/CMakeFiles/openxcom.dir/all] Error 2
Makefile:136: recipe for target 'all' failed
make: *** [all] Error

So it seems boost/shared_ptr.hpp is missing? So I search for topics on that, I find this: https://openxcom.org/forum/index.php/topic,2434.msg24474.html#msg24474 (https://openxcom.org/forum/index.php/topic,2434.msg24474.html#msg24474). I can't really make out how I am supposed to solve this issue (if its even the same?),

Quote from: FudgeDragon on June 30, 2014, 11:13:36 am

Following on from what SupSuper says, It also probably bears mentioning that depending on which version of yaml-cpp you've download you may need to change the names of the dependencies (in Properties->Configuration Properties->Linker->Input->Additional Dependencies) for your release and debug configurations.

In the new version of yaml-cpp the libraries are called libyaml-cppmd.lib (for release) and libyaml-cppmdd.lib (for debug)

OK, so I'm not sure how to do that. Or if I should. Help?

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 02:57:28 pm

AHA! This instruction (https://www.ufopaedia.org/index.php/Compiling_%28OpenXcom%29) was more comprehensive, I was missing some dependencies it seems, libboost-dev. Now building!

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 03:07:38 pm

Wait, why am I compiling openxcom-extended from source now again? ... I got it working anyhow, so now I can play openxcom (I tried it, works fine it seems, including starting a game)! BUT. I cannot play Piratez anyway can I ? :(

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 03:10:15 pm

Quote from: buenaventura on June 10, 2016, 02:57:28 pm

AHA! This instruction (https://www.ufopaedia.org/index.php/Compiling_%28OpenXcom%29) was more comprehensive, I was missing some dependencies it seems, libboost-dev. Now building!

libboost-dev is required only for vanilla OpenXcom

OpenXcom-Extended and OpenXcom-Extended-Plus... which is what you need... don't have a dependency on Boost anymore... but feel free to experiment, I'm sure you'll figure it out eventually

Quote from: buenaventura on June 10, 2016, 03:07:38 pm

Wait, why am I compiling openxcom-extended from source now again? ... I got it working anyhow, so now I can play openxcom (I tried it, works fine it seems, including starting a game)! BUT. I cannot play Piratez anyway can I ? :(

Again, if you want to play PirateZ, you need OpenXcom-Extended-Plus...
If you want to play just normal xcom game, OpenXcom is enough.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 03:14:56 pm

Quote from: Meridian on June 10, 2016, 03:10:15 pm

libboost-dev is required only for vanilla OpenXcom

OpenXcom-Extended and OpenXcom-Extended-Plus... which is what you need... don't have a dependency on Boost anymore... but feel free to experiment, I'm sure you'll figure it out eventually

Hum, well, perhaps I should first try compiling your special executable like you said. But where are these instructions? :

Quote from: Meridian on June 10, 2016, 11:01:05 am

X-PirateZ runs on custom executable, it comes either bundled with the game (v0.99), or in this thread: https://openxcom.org/forum/index.php/topic,4187.0.html or you can compile it on your own (directions in the same thread)

I sure can't find them in that thread.

Otherwise, do you have a link to a guide for compiling/getting openxcom-extended-plus, and the putting some Piratez on it?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 03:20:02 pm

Quote from: buenaventura on June 10, 2016, 03:14:56 pm

But where are these instructions?

I don't provide any official instructions, because I am not a linux guru.
But I do compile under Kubuntu 14.0 using these steps (and a few people have confirmed it is working for them too): https://openxcom.org/forum/index.php/topic,4187.msg65619.html#msg65619

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 03:21:53 pm

At the end of the first thread he posted, Meridian's extra resources for XPiratez, there are some instructions from a few of us who compiled his custom executable. Basically, download his source code, and make using the Makefile.simple in the src/ subfolder of his code.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 03:25:09 pm

Link for great justice: https://openxcom.org/forum/index.php/topic,4187.600.html

Edit: Follow Meridian's link, it'll point you straight to the post and he found it before I did. It works for Ubuntu 14.04 LTS in my case.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 03:33:05 pm

Thanks both of you, I am now compiling that. So the plan when it's done is to copy the executable into the 0.99 piratez-folder (which includes vanilla files from xcom:ufo defence i copied there) and try running it from there?

I guess someone should delete/replace that readme-folder in the archive as well as change this wiki page (https://www.ufopaedia.org/index.php/Info_%28Piratez%29#LINUX) to remove all those instructions if they are not correct. It is very tempting to believe they are!

Edit:
OK, compilation done. What now? Where is the executable?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 03:38:53 pm

Quote from: buenaventura on June 10, 2016, 03:33:05 pm

I guess someone should delete/replace that readme-folder in the archive as well as change this wiki page (https://www.ufopaedia.org/index.php/Info_%28Piratez%29#LINUX) to remove all those instructions if they are not correct. It is very tempting to believe they are!

I just don't feel qualified to do the instructions... I probably could do instructions for Kubuntu 14 (which is what I have installed on my PC since a few months), but if someone is using a different distribution, the instructions might not work...

We provide "foolproof" instructions for Windows users, and hope that Linux users know what they are doing...

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 03:55:58 pm

After compiling as above, I copied over the OpenXcom/bin/openxcom executable (that I just make'd) to the piratez-folder from the archive, and that ran as far as showing the intro movie and playing music, but then hung HARD, I couldn't even switch to virtual console or nothing, had to do hard reset. So I guess that was not the right thing to do ^__^'

Edit: If I get this to work, I will make sure to write something about it, that you can put there. Poor linux people! Anyway, instructions for Kubuntu would be fine, all the *ubuntu flavours work the same at that level I should think. And that is the most popular distribution.

Edit2: reading along in that thread you mentioned, I seem to have gotten the right executable after all. So why does it hang so badly on me :( This is what I've done:

1. extract archive with 0.99 piratez
2. add GEODATA etc. into UFO (patched and all)
3. compile Meridians OpenXCom to get the openxcom executable
4. put it in the piratez-folder (it has the right permissions set).

Shouldn't that work?

Edit3:
AH! Log file:

6-2016_14-48-59]   [INFO]   Data folder is:
[10-06-2016_14-48-59]   [INFO]   Data search is:
[10-06-2016_14-48-59]   [INFO]   - /home/simon/.local/share/openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/share/xubuntu/openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/share/xfce4/openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/local/sharehttps://openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/sharehttps://openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/share/openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/local/share/openxcom/
[10-06-2016_14-48-59]   [INFO]   - /usr/share/openxcom/
[10-06-2016_14-48-59]   [INFO]   - ./
[10-06-2016_14-48-59]   [INFO]   User folder is: ./user/
[10-06-2016_14-48-59]   [INFO]   Config folder is: /home/simon/.config/openxcom/
[10-06-2016_14-48-59]   [INFO]   Options loaded successfully.
[10-06-2016_14-48-59]   [INFO]   SDL initialized successfully.
[10-06-2016_14-48-59]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_14-48-59]   [INFO]   requested file not found: openxcom.png
[10-06-2016_14-48-59]   [INFO]   Attempting to set display to 1280x720x32...
[10-06-2016_14-49-00]   [INFO]   Display set to 1280x720x32.
[10-06-2016_14-49-00]   [INFO]   requested file not found: Shaders/raw.opengl.shader
[10-06-2016_14-49-00]   [ERROR]   Shaders/raw.opengl.shader: bad file
[10-06-2016_14-49-00]   [INFO]   requested file not found: Shaders/raw.opengl.shader
[10-06-2016_14-49-00]   [ERROR]   Shaders/raw.opengl.shader: bad file
[10-06-2016_14-49-00]   [INFO]   Loading data...
[10-06-2016_14-49-00]   [INFO]   Scanning standard mods in 'standard'...
[10-06-2016_14-49-00]   [INFO]   Scanning user mods in './user/mods'...
[10-06-2016_14-49-00]   [INFO]   removing references to missing mod: OpenXCom_Unlimited_Waypoints
[10-06-2016_14-49-00]   [INFO]   removing references to missing mod: TFTD_Damage
[10-06-2016_14-49-00]   [INFO]   removing references to missing mod: XCOM_Damage
[10-06-2016_14-49-00]   [INFO]   Mapping resource files...
[10-06-2016_14-49-00]   [INFO]   Resources files mapped successfully.
[10-06-2016_14-49-02]   [INFO]   Loading fonts... Font.dat
[10-06-2016_14-49-02]   [INFO]   Loading extra resources from ruleset...
[10-06-2016_14-49-02]   [INFO]   Data loaded successfully.
[10-06-2016_14-49-02]   [INFO]   Loading language...
[10-06-2016_14-49-02]   [INFO]   Language loaded successfully.
[10-06-2016_14-49-02]   [INFO]   OpenXcom started successfully!
[10-06-2016_14-49-02]   [INFO]   Playing flx, 320x200, 890 frames
[10-06-2016_14-49-03]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_14-49-03]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_14-49-04]   [FATAL]   A fatal error has occurred: signal 11
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x838fba5]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x83915ea]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x8057c47]
[10-06-2016_14-49-04]   [FATAL]   [0xb7754bc4]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x83b0206]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x844d0ed]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x81a9de6]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x81aa152]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x83879f5]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom(main+0x16b) [0x8054dbb]
[10-06-2016_14-49-04]   [FATAL]   /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xde) [0xb715a7ae]
[10-06-2016_14-49-04]   [FATAL]   /home/simon/games/OpenXcom_XPiratez/openxcom() [0x8056f93]

Huh?

Edit4:
AHA! I tried removing my config folder (.config/openxcom), and got just fatal error 11 :/ See here:

[10-06-2016_15-12-40]   [INFO]   Data folder is:
[10-06-2016_15-12-40]   [INFO]   Data search is:
[10-06-2016_15-12-40]   [INFO]   - /home/simon/.local/share/openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/share/xubuntu/openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/share/xfce4/openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/local/sharehttps://openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/sharehttps://openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/share/openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/local/share/openxcom/
[10-06-2016_15-12-40]   [INFO]   - /usr/share/openxcom/
[10-06-2016_15-12-40]   [INFO]   - ./
[10-06-2016_15-12-40]   [INFO]   User folder is: ./user/
[10-06-2016_15-12-40]   [INFO]   Config folder is: /home/simon/.config/openxcom/
[10-06-2016_15-12-40]   [INFO]   Options loaded successfully.
[10-06-2016_15-12-40]   [INFO]   SDL initialized successfully.
[10-06-2016_15-12-40]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_15-12-40]   [INFO]   requested file not found: openxcom.png
[10-06-2016_15-12-40]   [INFO]   Attempting to set display to 640x400x8...
[10-06-2016_15-12-40]   [INFO]   Display set to 640x400x8.
[10-06-2016_15-12-40]   [INFO]   Loading data...
[10-06-2016_15-12-40]   [INFO]   Scanning standard mods in 'standard'...
[10-06-2016_15-12-40]   [INFO]   Scanning user mods in './user/mods'...
[10-06-2016_15-12-40]   [INFO]   Mapping resource files...
[10-06-2016_15-12-40]   [INFO]   Resources files mapped successfully.
[10-06-2016_15-12-42]   [INFO]   Loading fonts... Font.dat
[10-06-2016_15-12-42]   [INFO]   Loading extra resources from ruleset...
[10-06-2016_15-12-42]   [INFO]   Data loaded successfully.
[10-06-2016_15-12-42]   [INFO]   Loading language...
[10-06-2016_15-12-42]   [INFO]   Language loaded successfully.
[10-06-2016_15-12-42]   [INFO]   OpenXcom started successfully!
[10-06-2016_15-12-42]   [INFO]   Playing flx, 320x200, 890 frames
[10-06-2016_15-12-42]   [INFO]   Using software scaling routine. For best results, try an OpenGL filter.
[10-06-2016_15-12-43]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_15-12-44]   [INFO]   SDL_mixer initialized successfully.
[10-06-2016_15-12-45]   [FATAL]   A fatal error has occurred: signal 11
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x838fba5]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x83915ea]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x8057c47]
[10-06-2016_15-12-45]   [FATAL]   [0xb775ebc4]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x83b0206]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x844d0ed]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x81a9de6]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x81aa152]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x83879f5]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom(main+0x16b) [0x8054dbb]
[10-06-2016_15-12-45]   [FATAL]   /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xde) [0xb71647ae]
[10-06-2016_15-12-45]   [FATAL]   ./openxcom() [0x8056f93]
[10-06-2016_15-12-50]   [FATAL]   OpenXcom has crashed: signal 11
Extra information has been saved to openxcom.log.
If this error was unexpected, please report it to the developers.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 04:18:47 pm

I don't know if it'll help for you, but I've had some success by using command line parameters to make sure I'm using the user and config files supplied by Dioxine. Try running the executable with

Code: [Select]

./OpenXcomEx -user "./user" -config "./user"
Replace ./OpenXcomEx with the executable name if it's something different for you, and make sure the OpenXcom_XPiratez folder you downloaded has options.cfg in the OpenXcom_XPiratez/user folder.

Edit: I generally create a bash script to run those command line parameters, placed in the same folder as the executable, just so I don't have to type the parameters every time.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 04:40:28 pm

Well, it was promising - it started up properly with your suggestion to include the paths, and the initial "Loading openxcom 1.0 dev", but it got stuck there. Mega stuck again, had to hard reset and no log was written :'(

Perhaps there is something wrong with the config I have in the ./user folder? :

mods:
- id: piratez
active: true
- id: xcom1
active: false
- id: Aliens_Pick_Up_Weapons
active: false
- id: Limit_Craft_Item_Capacities
active: false
- id: PSX_Static_Cydonia_Map
active: false
- id: UFOextender_Gun_Melee
active: false
- id: UFOextender_Psionic_Line_Of_Fire
active: false
- id: UFOextender_Starting_Avalanches
active: false
- active: false
id: XcomUtil_Always_Daytime
- id: XcomUtil_Always_Nighttime
active: false
- id: XcomUtil_Fighter_Transports
active: false
- id: XcomUtil_High_Explosive_Damage
active: false
- id: XcomUtil_Improved_Ground_Tanks
active: false
- id: XcomUtil_Improved_Heavy_Laser
active: false
- id: XcomUtil_No_Psionics
active: false
- id: XcomUtil_Pistol_Auto_Shot
active: false
- id: XcomUtil_Skyranger_Weapon_Slot
active: false
- active: false
id: XcomUtil_Starting_Defensive_Base
- id: XcomUtil_Starting_Defensive_Improved_Base
active: false
- id: XcomUtil_Starting_Improved_Base
active: false
- id: XcomUtil_Statstrings
active: false
- id: altSmokeOps
active: true
- id: altTacArmor
active: true
- active: false
id: altSGC
- id: Aliens_Pick_Up_Weapons_TFTD
active: false
- id: Limit_Craft_Item_Capacities_TFTD
active: false
- id: StrategyCore_Swap_Small_USOs_TFTD
active: false
- id: UFOextender_Gun_Melee_TFTD
active: false
- id: UFOextender_Psionic_Line_Of_Fire_TFTD
active: false
- id: XcomUtil_Always_Daytime_TFTD
active: false
- id: XcomUtil_Always_Nighttime_TFTD
active: false
- id: XcomUtil_High_Explosive_Damage_TFTD
active: false
- id: XcomUtil_Improved_Gauss
active: false
- id: XcomUtil_Infinite_Gauss
active: false
- id: XcomUtil_No_Psionics_TFTD
active: false
- id: XcomUtil_Pistol_Auto_Shot_TFTD
active: false
- id: XcomUtil_Starting_Defensive_Base_TFTD
active: false
- id: XcomUtil_Starting_Defensive_Improved_Base_TFTD
active: false
- id: XcomUtil_Starting_Improved_Base_TFTD
active: false
- active: true
id: piratezNaughtyMod
- id: altCorpses
active: false
options:
strafe: true
mousewheelSpeed: 3
changeValueByMouseWheel: 10
storageLimitsEnforced: true
displayWidth: 640
aggressiveRetaliation: false
asyncBlit: true
geoDragScrollButton: 2
useScaleFilter: false
useHQXFilter: false
useXBRZFilter: false
preferredMusic: 0
maximizeInfoScreens: true
vSyncForOpenGL: true
useOpenGLSmoothing: true
debug: true
useOpenGL: false
debugUi: false
preferredSound: 0
canSellLiveAliens: true
musicVolume: 0
language: en-US
canManufactureMoreItemsPerHour: true
battleScrollSpeed: 8
allowPsiStrengthImprovement: false
craftLaunchAlways: true
checkOpenGLErrors: false
useOpenGLShader: Shaders/5xbr_squared.opengl.shader
battleEdgeScroll: 2
battleDragScrollButton: 2
dragScrollPixelTolerance: 10
preferredVideo: 0
dragScrollTimeTolerance: 300
battleXcomSpeed: 23
battleAlienSpeed: 30
battleNewPreviewPath: 3
globeDetail: true
fpsCounter: false
geoDragScrollInvert: false
geoScrollSpeed: 28
globeRadarLines: true
musicAlwaysLoop: false
globeAllRadarsOnBaseBuild: true
soundVolume: 98
audioBitDepth: 16
pauseMode: 0
globeFlightPaths: false
playIntro: false
battleNotifyDeath: true
showFundsOnGeoscape: true
battleFireSpeed: 6
allowResize: false
windowedModePositionX: -1
windowedModePositionY: -1
borderless: false
captureMouse: true
autosave: true
keepAspectRatio: true
battleTooltips: true
nonSquarePixelRatio: false
audioSampleRate: 22050
cursorInBlackBandsInFullscreen: false
autosaveFrequency: 4
cursorInBlackBandsInWindow: true
cursorInBlackBandsInBorderlessWindow: false
saveOrder: 3
geoClockSpeed: 139
dogfightSpeed: 50
newSeedOnLoad: true
psiStrengthEval: false
uiVolume: 79
anytimePsiTraining: true
canTransferCraftsWhileAirborne: true
globeSeasons: true
allowBuildingQueue: true
displayHeight: 400
customInitialBase: false
geoscapeScale: 0
maxFrameSkip: 0
traceAI: false
keyboardMode: 1
battlescapeScale: 1
fullscreen: true
verboseLogging: false
StereoSound: true
battleHairBleach: true
keyScreenshot: 293
includePrimeStateInSavedLayout: true
battleConfirmFireMode: false
weaponSelfDestruction: false
allowPsionicCapture: true
alienBleeding: true
executeUnconsciousEnemies: true
twoHandedIndicator: true
minimapBorderIndicator: false
keyCancel: 27
keyGeoZoomIn: 43
keyGeoSpeed2: 50
keyGeoSpeed1: 49
everyoneFightsNobodyQuits: false
addVehiclesToMemorial: false
skipNextTurnScreen: true
TFTDDamage: false
noAlienPanicMessages: false
fieldPromotions: true
battleDragScrollInvert: false
sneakyAI: false
battleUFOExtenderAccuracy: true
showMoreStatsInInventoryView: true
battleSmoothCamera: false
keyQuickSave: 286
keyQuickLoad: 290
keyFps: 288
disableAutoEquip: false
keyBattleCenterEnemy7: 55
keyBattleCenterEnemy8: 56
keyBattleCenterEnemy9: 57
keyBattleCenterEnemy10: 48
keyBattleVoxelView: 291
keyInvCreateTemplate: 99
keyBattleActionItem3: 51
keyBattleActionItem2: 50
keyBattleActionItem1: 49
keyInvClear: 98
keyBattlePersonalLighting: 108
keyBattleReserveNone: 282
keyBattleZeroTUs: 127
keyBattleCenterEnemy3: 51
keyBattleActionItem5: 53
FPSInactive: 30
keyInvApplyTemplate: 118
FPS: 60
keyBattleCenterEnemy4: 52
keyBattleCenterEnemy6: 54
keyBattleCenterEnemy5: 53
keyBattleActionItem4: 52
keyToggleQuickSearch: 113
battleExplosionHeight: 2
battleAutoEnd: true
forceFire: true
spendResearchedItems: true
battleInstantGrenade: false
bleedingIndicator: true
statisticalBulletConservation: true
keyBaseSelect7: 55
keyGeoSpeed4: 52
keyGeoSpeed3: 51
showItemNameAndWeightInInventory: false
showGunMeleeOnTop: false
showQuickSearch: true
keyOk: 13
keyGeoLeft: 276
keyBaseSelect1: 49
keyBaseSelect2: 50
keyGeoToggleRadar: 114
keyGeoRight: 275
keyGeoUp: 273
keyGeoDown: 274
keyGeoZoomOut: 45
keyBattleLeft: 276
keyGeoSpeed5: 53
keyBattleUp: 273
keyBaseSelect8: 56
keyGeoSpeed6: 54
keyGeoIntercept: 105
keyGeoBases: 98
keyGeoGraphs: 103
keyBattleLevelUp: 280
keyBattleDown: 274
keyGeoUfopedia: 117
keyGeoOptions: 27
keyGeoFunding: 102
keyGeoToggleDetail: 9
keyBaseSelect3: 51
keyBaseSelect4: 52
keyBattleAbort: 97
keyBattleEndTurn: 8
keyBaseSelect5: 53
keyBaseSelect6: 54
keyBattleRight: 275
keyBattleLevelDown: 281
keyBattleReserveSnap: 283
keyBattleReserveAuto: 285
keyBattleReserveKneel: 106
keyBattleMap: 109
keyBattleReserveAimed: 284
keyBattleCenterUnit: 278
keyBattlePrevUnit: 122
keyBattleNextUnit: 120
keyBattleDeselectUnit: 32
keyBattleUseLeftHand: 113
keyBattleCenterEnemy2: 50
keyBattleCenterEnemy1: 49
keyBattleUseRightHand: 101
keyBattleInventory: 105
keyBattleOptions: 27
keyBattleStats: 115
keyBattleKneel: 107
keyBattleReload: 114

Perhaps ohartenstein23 can post his executable, and I could try it out?

Perhaps I should work on the one supplied by Meridian instead, I get this error with it:

simon@simon-Aspire-E5-521G:~/games/OpenXcom_XPiratez$ ./OpenXcomExPlusElf -user "./user" -config "./user"
./OpenXcomExPlusElf: symbol lookup error: ./OpenXcomExPlusElf: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarE

Any suggestions?

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 04:49:30 pm

The config looks a little strange on a few lines under mods:, where the id: and active: tags seem to be reversed. Try switching the following lines

Code: [Select]

  - active: false
    id: XcomUtil_Always_Daytime

  - active: false
    id: XcomUtil_Starting_Defensive_Base

  - active: false
    id: altSGC

  - active: true
    id: piratezNaughtyMod

with

Code: [Select]

  - id: XcomUtil_Always_Daytime
    active: false

  - id: XcomUtil_Starting_Defensive_Base
    active: false

  - id: altSGC
    active: false

  - id: piratezNaughtyMod
    active: true

Here's a link to my executable:
https://drive.google.com/file/d/0BzdM3YhNg14pc0VmakR2bUxqQ2c/view?usp=sharing

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 10, 2016, 05:10:25 pm

I did the replacements as you suggested, to no avail, no difference. It says "Loading OpenXCom 1.0 Dev ..." with a blinking cursor, then the cursor stops blinking, and then BAM, totally dead. Hard reset. Thank you for the executable - its compiled for 64-bit, so no go there (I am on 32-bit). Perhaps that is the problem? Any other suggestions? Is there a checksum for the archive of piratez that I could check, in case it was corrupted?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 05:53:29 pm

Do you even have the correct source code?
Can you please locate the "version.h" file and copy-paste the whole file here please? So that I can check if it's the right version...

EDIT:
You should not see "Loading OpenXcom 1.0 Dev ...", it should be "Loading OpenXcom Extended 2.9+ ..." ... see screenshot.
After loaded, it should look something like attached.

Title: Re: Segmentation fault (core dumped) on starting
Post by: Yankes on June 10, 2016, 09:02:25 pm

Quote from: buenaventura on June 10, 2016, 04:40:28 pm

Perhaps I should work on the one supplied by Meridian instead, I get this error with it:

simon@simon-Aspire-E5-521G:~/games/OpenXcom_XPiratez$ ./OpenXcomExPlusElf -user "./user" -config "./user"
./OpenXcomExPlusElf: symbol lookup error: ./OpenXcomExPlusElf: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarE

Any suggestions?

This probably mean that you lack correct yaml lib used by Meridian binary. If you have already installed `yaml-cpp` (e.g. something like `apt-get install libyaml-cpp0.5`) then you have incompatible version.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 09:24:00 pm

Hey Meridian, do you know offhand what version of the yaml library you're using? Or, could you post the output from listing the package in an Ubuntu terminal, using a command like

Code: [Select]

dpkg -l | grep libyaml

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 09:40:52 pm

Version I use to compile the Windows binary is the one from the master branch (definitely after v0.5.3, already without boost), checked out from github on March 28th 2016.
Commit ID: 178c8d1f276afeec006e2c4e1dfa979c1f9d2a3c

As for the output of the command you provided, see attached screenshot.

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 10:11:34 pm

Hmm, I just clicked on that system update message you see above... tried to update the system... and the system didn't survive it.
I get until login screen and after that just blackness and mouse cursor... can't do anything at all.
Any ideas?

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 11:15:40 pm

Those are the same version of the yaml library that I have, although you have the 32-bit ones (i386). @buenaventura, what do you get as output from the same command? Did you install the dev version before compiling (libyaml-cpp-dev)?

As for the system update, I haven't ever run a linux system as a virtual machine, and I don't have any experience with Kubuntu, so... somebody else got an idea?

Edit: @Meridian, wait, try pressing Ctl+Alt+F1 when you get to the mouse cursor? That should bring up terminal-style input/output without the graphical desktop environment, it may help you troubleshoot from there. After that, google's knowledge is better than mine at fixing this one.

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 10, 2016, 11:22:29 pm

Yeah, no need for ideas anymore I think... I tried to repair it, but now I get just a few hexadecimal octets at start without command prompt, login screen or anything interactive. It's dead. RIP.

This means I won't be releasing new versions for a few weeks (unless I ask someone else to compile), until I will have time and nerves to reinstall everything again.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 10, 2016, 11:26:10 pm

Ouch, time to add Meridian's Kubuntu virtual box to the memorial wall.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 11, 2016, 12:41:34 am

If you'd like, I could compile for 64-bit Ubuntu distribution, but you'd probably have to find somebody else for 32-bit... @buenaventura, have you got it to work yet on your system?

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 11, 2016, 01:00:06 pm

Hello again everyone,

Regarding version, that is suspicions. Where is the version.h file? I cant find it.

Regarding libyaml (which seems the most promising approach after all), this is my output:

ii libyaml-cpp-dev 0.5.3~3~ubuntu15.10.1 i386 YAML parser and emitter for C++ - development files
ii libyaml-cpp0.5v5:i386 0.5.3~3~ubuntu15.10.1 i386 YAML parser and emitter for C++
ii libyaml-tiny-perl 1.69-1 all Perl module for reading and writing YAML files

I've gotten my libyaml from this launchpad: https://launchpad.net/~winterheart/+archive/ubuntu/openxcom (https://launchpad.net/~winterheart/+archive/ubuntu/openxcom). Seems right?

I'll be back next week latest, have'nt got much time now!

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 11, 2016, 02:24:25 pm

Quote from: buenaventura on June 11, 2016, 01:00:06 pm

Regarding version, that is suspicions. Where is the version.h file? I cant find it.

1. are you compiling your own executable?

- if yes, search in folder "src"
- if not, see point 2.

2. vanilla OpenXcom does not support PirateZ, please don't even try; OpenXcom-Extended (from mod portal) also does not support PirateZ, please don't waste your time!!

You need either:
a/ the executable shipped directly with PirateZ (v0.99)
b/ or the executable from the my thread
c/ or you can compile the same executable directly from sources

If you don't see the loading screen with the same version as pictured in my previous post, you are wasting both your and our time...

Title: Re: Segmentation fault (core dumped) on starting
Post by: Yankes on June 11, 2016, 03:34:46 pm

Quote from: buenaventura on June 11, 2016, 01:00:06 pm

Hello again everyone,

Regarding version, that is suspicions. Where is the version.h file? I cant find it.

Regarding libyaml (which seems the most promising approach after all), this is my output:

ii libyaml-cpp-dev 0.5.3~3~ubuntu15.10.1 i386 YAML parser and emitter for C++ - development files
ii libyaml-cpp0.5v5:i386 0.5.3~3~ubuntu15.10.1 i386 YAML parser and emitter for C++
ii libyaml-tiny-perl 1.69-1 all Perl module for reading and writing YAML files

I've gotten my libyaml from this launchpad: https://launchpad.net/~winterheart/+archive/ubuntu/openxcom (https://launchpad.net/~winterheart/+archive/ubuntu/openxcom). Seems right?

I'll be back next week latest, have'nt got much time now!

Meridian binary is compiled against older version of yaml-cpp (at leas he have only 0.5.1 on his machine). I don't know is possible easy install older version on your machine.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 12, 2016, 12:19:23 pm

Quote from: Yankes on June 11, 2016, 03:34:46 pm

Meridian binary is compiled against older version of yaml-cpp (at leas he have only 0.5.1 on his machine). I don't know is possible easy install older version on your machine.

Well, this seems to be the problem then, doing a fresh dowload, unraring, copying steam files (that are patched with the patch available here: https://openxcom.org/downloads-extras/ ) and then running the bundled executable (supplying ./OpenXcomExPlusElf -user "./user" -config "./user") gives:

./OpenXcomExPlusElf: symbol lookup error: ./OpenXcomExPlusElf: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarE

So I try the one you supply in the thread (what's the difference by the way?), gives the identical response. So I guess I should start there. What EXACT version of libyaml-cpp should I have then?

Edit: I don't want to waste anyone's time or anything, just help me if you have spare. I'll be sure to give back once I get this going!

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 12, 2016, 02:39:44 pm

Okay, I've gotten hold of libyaml-cpp and -dev version 0.5.1 (from Trusty Tahr repositories, downloaded here: https://packages.ubuntu.com/trusty/i386/libyaml-cpp0.5/download and installed with dpkg -i, I removed all other versions first). Now I do not get the previous error (./OpenXcomExPlusElf: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarE) yay, now I just get:

Failed to open directory:

With no directory specified, just like that. Wierd huh? At least it seems happy about my libyaml-cpp version. I've given -user "./user" -config "./user" -data "./" so it should find those. I've tried both with the bundled executable and with the one from Meridians thread, same thing (compiling my own I might try next, if you think it might make any difference). Any ideas?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Yankes on June 12, 2016, 03:05:51 pm

It look as it try open directory from empty path, could you call exe without arguments or pass in absolute directory paths?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 12, 2016, 09:38:22 pm

Maybe try this:

Quote from: Stoddard on June 12, 2016, 08:55:18 pm

I set up a buildbot that builds binaries on the three current ubuntu releases. Results can be had here: https://lxnt.wtf/oxem/

The bot should pick up any changes in github repo in a day or so.

Libyaml is 0.5.3 statically linked. Libsdl1.2 is pretty much the same across the releases, so the main difference would be the compilers, and gcc 5.2/5.3 spits way more warnings (than 4.8 in trusty).

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 13, 2016, 09:39:58 am

Quote from: Yankes on June 12, 2016, 03:05:51 pm

It look as it try open directory from empty path, could you call exe without arguments or pass in absolute directory paths?

I tried with absolute paths, like this:
./OpenXcomExPlusElf -data "/home/simon/Downloads/OpenXcom_XPiratez/UFO" -user "/home/simon/Downloads/OpenXcom_XPiratez" -config "/home/simon/Downloads/OpenXcom_XPiratez"

And I got a new result, see attached .png. Progress! But what now? libyaml-cpp 0.5.1 (from Trusty Tahr repos) gives that, while 0.5.3~3 (from winterhearts repo (https://launchpad.net/~winterheart/+archive/ubuntu/openxcom)) gives the other error above. Should I try some other libyaml?

The executable Meridian suggested gives identical response as the other one (see attachment), so libyaml-cpp seems to be the culprit. Unless I need to move something more than these to the UFO folder:
simon@simon-Aspire-E5-521G:~/Downloads/OpenXcom_XPiratez/UFO$ ls -a
. .. GEODATA GEOGRAPH MAPS ROUTES SOUND TERRAIN UFOGRAPH UNITS
I don't trust the readme's (https://www.ufopaedia.org/index.php/Installing_%28OpenXcom%29#All_platforms), so I might as well ask :)

Edit: I found this: https://openxcom.org/bugs/openxcom/issues/666 (https://openxcom.org/bugs/openxcom/issues/666) (omnious! the devil's issue), related? But I give the path to the config when I invoke? ...
Edit2: https://stackoverflow.com/questions/23108179/how-to-load-yaml-file-via-yaml-cpp - It might not be missing the config, but simply not able to parse something, like the answer suggests? Below is the config:

options:
displayWidth: 1680
displayHeight: 1050
fullscreen: true
asyncBlit: true
keyboardMode: 1
maxFrameSkip: 0
traceAI: false
verboseLogging: false
StereoSound: true
geoscapeScale: 0
battlescapeScale: 1
useScaleFilter: false
useHQXFilter: false
useXBRZFilter: false
useOpenGL: false
checkOpenGLErrors: false
useOpenGLShader: Shaders/5xbr_squared.opengl.shader
vSyncForOpenGL: true
useOpenGLSmoothing: true
debug: true
debugUi: false
soundVolume: 98
musicVolume: 0
uiVolume: 79
language: en-US
battleScrollSpeed: 8
battleEdgeScroll: 2
battleDragScrollButton: 2
dragScrollTimeTolerance: 300
dragScrollPixelTolerance: 10
battleFireSpeed: 6
battleXcomSpeed: 23
battleAlienSpeed: 30
battleNewPreviewPath: 3
fpsCounter: false
globeDetail: true
globeRadarLines: true
globeFlightPaths: false
globeAllRadarsOnBaseBuild: true
audioSampleRate: 22050
audioBitDepth: 16
pauseMode: 0
battleNotifyDeath: true
showFundsOnGeoscape: true
allowResize: false
windowedModePositionX: -1
windowedModePositionY: -1
borderless: false
captureMouse: true
keyBattleCenterEnemy3: 51
battleTooltips: true
keepAspectRatio: true
nonSquarePixelRatio: false
cursorInBlackBandsInFullscreen: false
cursorInBlackBandsInWindow: true
cursorInBlackBandsInBorderlessWindow: false
saveOrder: 3
geoClockSpeed: 139
dogfightSpeed: 50
geoScrollSpeed: 28
geoDragScrollButton: 2
preferredMusic: 0
preferredSound: 0
preferredVideo: 0
musicAlwaysLoop: false
playIntro: false
autosave: true
autosaveFrequency: 4
newSeedOnLoad: true
mousewheelSpeed: 3
changeValueByMouseWheel: 10
maximizeInfoScreens: true
geoDragScrollInvert: false
aggressiveRetaliation: false
customInitialBase: false
allowBuildingQueue: true
craftLaunchAlways: true
storageLimitsEnforced: true
canSellLiveAliens: true
anytimePsiTraining: true
globeSeasons: true
psiStrengthEval: false
canTransferCraftsWhileAirborne: true
canManufactureMoreItemsPerHour: true
spendResearchedItems: true
fieldPromotions: true
battleDragScrollInvert: false
sneakyAI: false
showMoreStatsInInventoryView: true
battleHairBleach: true
battleInstantGrenade: false
includePrimeStateInSavedLayout: true
battleUFOExtenderAccuracy: true
battleExplosionHeight: 2
weaponSelfDestruction: false
battleSmoothCamera: false
disableAutoEquip: false
battleConfirmFireMode: false
battleAutoEnd: true
allowPsionicCapture: true
allowPsiStrengthImprovement: false
strafe: true
forceFire: true
skipNextTurnScreen: true
TFTDDamage: false
noAlienPanicMessages: false
alienBleeding: true
executeUnconsciousEnemies: true
twoHandedIndicator: true
minimapBorderIndicator: false
everyoneFightsNobodyQuits: false
addVehiclesToMemorial: false
bleedingIndicator: true
statisticalBulletConservation: true
showItemNameAndWeightInInventory: false
showGunMeleeOnTop: false
showQuickSearch: true
keyOk: 13
keyCancel: 27
keyScreenshot: 293
keyGeoRight: 275
keyQuickSave: 286
keyQuickLoad: 290
keyGeoLeft: 276
keyFps: 288
keyGeoUp: 273
keyGeoDown: 274
keyGeoZoomIn: 43
keyGeoZoomOut: 45
keyGeoSpeed1: 49
keyGeoSpeed2: 50
keyGeoSpeed3: 51
keyGeoSpeed4: 52
keyGeoSpeed5: 53
keyGeoIntercept: 105
keyGeoBases: 98
keyGeoGraphs: 103
keyGeoSpeed6: 54
keyGeoUfopedia: 117
keyGeoOptions: 27
keyGeoFunding: 102
keyGeoToggleDetail: 9
keyGeoToggleRadar: 114
keyBaseSelect1: 49
keyBaseSelect2: 50
keyBaseSelect3: 51
keyBaseSelect4: 52
keyBaseSelect6: 54
keyBaseSelect7: 55
keyBaseSelect8: 56
keyBattleLeft: 276
keyBaseSelect5: 53
keyBattleRight: 275
keyBattleDown: 274
keyBattleLevelUp: 280
keyBattleLevelDown: 281
keyBattleUp: 273
keyBattleCenterUnit: 278
keyBattlePrevUnit: 122
keyBattleNextUnit: 120
keyBattleUseLeftHand: 113
keyBattleUseRightHand: 101
keyBattleInventory: 105
keyBattleDeselectUnit: 32
keyBattleMap: 109
keyBattleOptions: 27
keyBattleEndTurn: 8
keyBattleStats: 115
keyBattleKneel: 107
keyBattleReload: 114
keyBattlePersonalLighting: 108
keyBattleAbort: 97
keyBattleReserveNone: 282
keyBattleReserveSnap: 283
keyBattleReserveAimed: 284
keyBattleReserveAuto: 285
keyBattleReserveKneel: 106
keyBattleZeroTUs: 127
keyBattleCenterEnemy1: 49
keyBattleCenterEnemy2: 50
keyBattleCenterEnemy4: 52
keyBattleCenterEnemy5: 53
keyBattleCenterEnemy6: 54
keyBattleCenterEnemy7: 55
keyBattleCenterEnemy8: 56
keyBattleCenterEnemy9: 57
keyBattleCenterEnemy10: 48
keyBattleVoxelView: 291
keyInvCreateTemplate: 99
keyInvApplyTemplate: 118
keyInvClear: 98
keyBattleActionItem1: 49
keyBattleActionItem2: 50
keyBattleActionItem3: 51
keyBattleActionItem4: 52
keyBattleActionItem5: 53
keyToggleQuickSearch: 113
FPS: 60
FPSInactive: 30
mods:
- id: piratez
active: true
- id: xcom1
active: false
- id: 40k
active: true
- id: Aliens_Pick_Up_Weapons
active: false
- id: Limit_Craft_Item_Capacities
active: false
- id: PSX_Static_Cydonia_Map
active: false
- id: UFOextender_Gun_Melee
active: false
- id: UFOextender_Psionic_Line_Of_Fire
active: false
- id: UFOextender_Starting_Avalanches
active: false
- id: XcomUtil_Always_Daytime
active: false
- id: XcomUtil_Always_Nighttime
active: false
- id: XcomUtil_Fighter_Transports
active: false
- id: XcomUtil_High_Explosive_Damage
active: false
- id: XcomUtil_Improved_Ground_Tanks
active: false
- id: XcomUtil_Improved_Heavy_Laser
active: false
- id: XcomUtil_No_Psionics
active: false
- id: XcomUtil_Pistol_Auto_Shot
active: false
- id: XcomUtil_Skyranger_Weapon_Slot
active: false
- id: XcomUtil_Starting_Defensive_Base
active: false
- id: XcomUtil_Starting_Defensive_Improved_Base
active: false
- id: XcomUtil_Starting_Improved_Base
active: false
- id: XcomUtil_Statstrings
active: false
- id: altSmokeOps
active: true
- id: altTacArmor
active: true
- id: altSGC
active: false
- id: Aliens_Pick_Up_Weapons_TFTD
active: false
- id: Limit_Craft_Item_Capacities_TFTD
active: false
- id: StrategyCore_Swap_Small_USOs_TFTD
active: false
- id: UFOextender_Gun_Melee_TFTD
active: false
- id: UFOextender_Psionic_Line_Of_Fire_TFTD
active: false
- id: XcomUtil_Always_Daytime_TFTD
active: false
- id: XcomUtil_Always_Nighttime_TFTD
active: false
- id: XcomUtil_High_Explosive_Damage_TFTD
active: false
- id: XcomUtil_Improved_Gauss
active: false
- id: XcomUtil_Infinite_Gauss
active: false
- id: XcomUtil_No_Psionics_TFTD
active: false
- id: XcomUtil_Pistol_Auto_Shot_TFTD
active: false
- id: XcomUtil_Starting_Defensive_Base_TFTD
active: false
- id: XcomUtil_Starting_Defensive_Improved_Base_TFTD
active: false
- id: XcomUtil_Starting_Improved_Base_TFTD
active: false
- id: piratezNaughtyMod
active: true
- id: altCorpses
active: false
- id: ocpgranny
active: false

Edit3: yaml-cpp obv. sucks. ;) (https://ciaranm.wordpress.com/2009/03/01/yaml-sucks-gems-sucks-syck-sucks/) Perhaps I should try to build the latest version myself? But then how do I tell the piratez to use it? (github (https://github.com/jbeder/yaml-cpp)). I'll stop spamming now and wait for some suggestions from you guys.

Title: Re: Segmentation fault (core dumped) on starting
Post by: ohartenstein23 on June 13, 2016, 03:06:29 pm

Hi buenaventura, here's another thread you might want to watch for more information on linux versions of OXCE+ (Meridian's version of the executable) and how it works with XPiratez. https://openxcom.org/forum/index.php/topic,4526.0.html

At this point, you should try compiling a fresh executable with the 0.5.1 libraries. If you put the compiled file in the XPiratez folder, same location as the windows .exe file, you shouldn't have to specify the data folder - it'll search the correct directory automatically. You should also specify the user and config file paths as "/home/Simon/Downloads/OpenXcom_XPiratez/user" - it's not always necessary to do so, since the code should search for that directory, but it may help. The mod files are contained in the user folder, and enabling it will be in the options menu once you get the executable working.

Title: Re: Segmentation fault (core dumped) on starting
Post by: Arthanor on June 13, 2016, 04:23:22 pm

Nothing that I know of in the original game uses yaml, so a yaml error is an issue with some openxcom files (or your yaml version). Make sure that you've got the rulesets and config files in the right places.

I've got to say, this seems to be way more complicated than it should be. I typically install using CMAKE (https://www.ufopaedia.org/index.php/Compiling_with_CMake_(OpenXcom)), and it has been very reliable.

Last time, I used this command to get my dependenciy:
apt-get install --no-install-recommends \ build-essential libboost-dev libsdl1.2-dev libsdl-mixer1.2-dev \ libsdl-image1.2-dev libsdl-gfx1.2-dev libyaml-cpp-dev xmlto

But for some reason the game wouldn't play music, so I had to install timidity as well, which you have already done, I think.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 13, 2016, 04:40:16 pm

Quote from: ohartenstein23 on June 13, 2016, 03:06:29 pm

Hi buenaventura, here's another thread you might want to watch for more information on linux versions of OXCE+ (Meridian's version of the executable) and how it works with XPiratez. https://openxcom.org/forum/index.php/topic,4526.0.html

At this point, you should try compiling a fresh executable with the 0.5.1 libraries. If you put the compiled file in the XPiratez folder, same location as the windows .exe file, you shouldn't have to specify the data folder - it'll search the correct directory automatically. You should also specify the user and config file paths as "/home/Simon/Downloads/OpenXcom_XPiratez/user" - it's not always necessary to do so, since the code should search for that directory, but it may help. The mod files are contained in the user folder, and enabling it will be in the options menu once you get the executable working.

Hi, thanks, I've tried to compile with libyaml-cpp-dev 0.5.1 (from here (https://packages.ubuntu.com/trusty/i386/libyaml-cpp-dev/download)), after cloning from meridian's git but alas, that libyaml seems to cause problems still... (see the bottom of this tail of the output from make -f -j10 Makefile.simple:

<snipped ALOT of output>
Options.cpp:(.text+0x10911): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Options.cpp:(.text+0x10b5a): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Options.cpp:(.text+0x110e2): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/Options.o: In function `OpenXcom::Options::userSplitMasters()':
Options.cpp:(.text+0x11fdb): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/Options.o: In function `OpenXcom::Options::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
Options.cpp:(.text+0x14604): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/Language.o: In function `OpenXcom::Language::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
Language.cpp:(.text+0x65f1): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/OpenGL.o: In function `OpenXcom::OpenGL::set_shader(char const*)':
OpenGL.cpp:(.text+0x392a): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/ModInfo.o: In function `OpenXcom::ModInfo::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
ModInfo.cpp:(.text+0x4a5): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/OptionInfo.o: In function `OpenXcom::OptionInfo::save(YAML::Node&) const':
OptionInfo.cpp:(.text+0x20b9): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
OptionInfo.cpp:(.text+0x22c0): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
OptionInfo.cpp:(.text+0x24c4): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
../obj/OptionInfo.o: In function `YAML::Node YAML::Node::operator[]<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
OptionInfo.cpp:(.text._ZN4YAML4NodeixINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEES0_RKT_[_ZN4YAML4NodeixINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEES0_RKT_]+0x621): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
collect2: error: ld returned 1 exit status
Makefile.simple:47: recipe for target '../bin/openxcom' failed
make: *** [../bin/openxcom] Error 1

)

dpkg -l | grep libyaml-cpp gives:

ii libyaml-cpp-dev 0.5.1-1 i386 YAML parser and emitter for C++ - development files
rc libyaml-cpp0.3v5:i386 0.3.0-1.2 i386 YAML parser and emitter for C++ (0.3 series)
ii libyaml-cpp0.5:i386 0.5.1-1 i386 YAML parser and emitter for C++
rc libyaml-cpp0.5v5:i386 0.5.3~3~ubuntu15.10.1 i386 YAML parser and emitter for C++

Quote from: Arthanor on June 13, 2016, 04:23:22 pm

Nothing that I know of in the original game uses yaml, so a yaml error is an issue with some openxcom files (or your yaml version). Make sure that you've got the rulesets and config files in the right places.

I've got to say, this seems to be way more complicated than it should be. I typically install using CMAKE (https://www.ufopaedia.org/index.php/Compiling_with_CMake_(OpenXcom)), and it has been very reliable.

Last time, I used this command to get my dependenciy:
apt-get install --no-install-recommends \ build-essential libboost-dev libsdl1.2-dev libsdl-mixer1.2-dev \ libsdl-image1.2-dev libsdl-gfx1.2-dev libyaml-cpp-dev xmlto

How can I make sure about rulesets and such? (I don't know exactly what you mean there).

I'm cloning again now to try with CMake, but I did that before as well though. (You used this git? : git clone https://github.com/MeridianOXC/OpenXcom.git ). Yeah this seems more complicated than it should be - if I did not find this quite fun/interesting, and if I was not currently at work (*snickers*), I would probably not go through so much trouble!

Edit: Oops, forget the stuff about compilation not working, forgot some stuff. Doing Cmake now which should work better I hope.

Title: Re: Segmentation fault (core dumped) on starting
Post by: Meridian on June 13, 2016, 04:54:48 pm

Quote from: buenaventura on June 13, 2016, 04:40:16 pm

I'm cloning again now to try with CMake, but I did that before as well though. (You used this git? : git clone https://github.com/MeridianOXC/OpenXcom.git ). Yeah this seems more complicated than it should be - if I did not find this quite fun/interesting, and if I was not currently at work (*snickers*), I would probably not go through so much trouble!

I just hope you're not using the "master" branch, but the "oxce2.9-plus-proto" branch (I never got the answer about version.h from you).
The master is just an old copy of vanilla openxcom and won't help you.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 13, 2016, 05:09:18 pm

Quote from: Meridian on June 13, 2016, 04:54:48 pm

I just hope you're not using the "master" branch, but the "oxce2.9-plus-proto" branch (I never got the answer about version.h from you).
The master is just an old copy of vanilla openxcom and won't help you.

OF COURSE NOT I WOULD NEV... ;D
* git clone https://github.com/MeridianOXC/OpenXcom.git oxce2.9-plus-proto *
building now...

Dang! So close! :

<snip>
NewBattleState.cpp:(.text._ZN4YAML4NodeaSIjEERS0_RKT_[_ZN4YAML4NodeaSIjEERS0_RKT_]+0x375): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Menu/NewBattleState.cpp.o: In function `YAML::Node YAML::Node::operator[]<char [5]>(char const (&) [5])':
NewBattleState.cpp:(.text._ZN4YAML4NodeixIA5_cEES0_RKT_[_ZN4YAML4NodeixIA5_cEES0_RKT_]+0x527): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Mod/Armor.cpp.o: In function `OpenXcom::Armor::load(YAML::Node const&)':
Armor.cpp:(.text+0x3e62): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/MapScript.cpp.o: In function `OpenXcom::MapScript::load(YAML::Node const&)':
MapScript.cpp:(.text+0x415b): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/Mod.cpp.o: In function `YAML::Node::Scalar[abi:cxx11]() const [clone .isra.734]':
Mod.cpp:(.text+0xd19): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/Mod.cpp.o: In function `OpenXcom::Mod::loadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
Mod.cpp:(.text+0xef71): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Mod/Mod.cpp.o: In function `OpenXcom::Mod::loadExtraResources()':
Mod.cpp:(.text+0x210ff): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Mod/RuleMissionScript.cpp.o: In function `YAML::Node::Scalar[abi:cxx11]() const [clone .isra.100]':
RuleMissionScript.cpp:(.text+0x6a9): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/RuleRegion.cpp.o: In function `OpenXcom::RuleRegion::load(YAML::Node const&)':
RuleRegion.cpp:(.text+0x1993): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
RuleRegion.cpp:(.text+0x199d): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
RuleRegion.cpp:(.text+0x19b4): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/RuleSoldier.cpp.o: In function `OpenXcom::RuleSoldier::load(YAML::Node const&, OpenXcom::Mod*)':
RuleSoldier.cpp:(.text+0x3279): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Mod/RuleSoldier.cpp.o:RuleSoldier.cpp:(.text+0x3283): more undefined references to `YAML::detail::node_data::empty_scalar[abi:cxx11]' follow
CMakeFiles/openxcom.dir/Mod/SoldierNamePool.cpp.o: In function `OpenXcom::SoldierNamePool::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
SoldierNamePool.cpp:(.text+0x1b41): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/AlienBase.cpp.o: In function `OpenXcom::AlienBase::save() const':
AlienBase.cpp:(.text+0x147a): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
AlienBase.cpp:(.text+0x1666): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
AlienBase.cpp:(.text+0x193e): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
AlienBase.cpp:(.text+0x1e69): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
AlienBase.cpp:(.text+0x2348): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/AlienBase.cpp.o:AlienBase.cpp:(.text+0x2700): more undefined references to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' follow
CMakeFiles/openxcom.dir/Savegame/AlienStrategy.cpp.o: In function `OpenXcom::AlienStrategy::save() const':
AlienStrategy.cpp:(.text+0x31f1): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/AlienStrategy.cpp.o: In function `void YAML::Node::Assign<std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, int> > > >(std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, int> > > const&)':
AlienStrategy.cpp:(.text._ZN4YAML4Node6AssignISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiSt4lessIS8_ESaISt4pairIKS8_iEEEEEvRKT_[_ZN4YAML4Node6AssignISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiSt4lessIS8_ESaISt4pairIKS8_iEEEEEvRKT_]+0x1f0): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/AlienStrategy.cpp.o: In function `YAML::convert<std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > > > > > >::decode(YAML::Node const&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > > > > >&)':
AlienStrategy.cpp:(.text._ZN4YAML7convertISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorISt4pairIS7_iESaISA_EESt4lessIS7_ESaIS9_IKS7_SC_EEEE6decodeERKNS_4NodeERSI_[_ZN4YAML7convertISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorISt4pairIS7_iESaISA_EESt4lessIS7_ESaIS9_IKS7_SC_EEEE6decodeERKNS_4NodeERSI_]+0x4a1): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/AlienStrategy.cpp.o: In function `void YAML::detail::node_data::force_insert<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > > >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int>, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int> > > const&, boost::shared_ptr<YAML::detail::memory_holder>)':
AlienStrategy.cpp:(.text._ZN4YAML6detail9node_data12force_insertINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorISt4pairIS8_iESaISB_EEEEvRKT_RKT0_N5boost10shared_ptrINS0_13memory_holderEEE[_ZN4YAML6detail9node_data12force_insertINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorISt4pairIS8_iESaISB_EEEEvRKT_RKT0_N5boost10shared_ptrINS0_13memory_holderEEE]+0xeb): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Base.cpp.o: In function `OpenXcom::Base::saveId() const':
Base.cpp:(.text+0x8aa9): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Base.cpp.o: In function `YAML::Node::Node<char [6]>(char const (&) [6])':
Base.cpp:(.text._ZN4YAML4NodeC2IA6_cEERKT_[_ZN4YAML4NodeC5IA6_cEERKT_]+0x158): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/BaseFacility.cpp.o: In function `OpenXcom::BaseFacility::save() const':
BaseFacility.cpp:(.text+0x151e): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/BaseFacility.cpp.o: In function `YAML::Node YAML::Node::operator[]<char [10]>(char const (&) [10])':
BaseFacility.cpp:(.text._ZN4YAML4NodeixIA10_cEES0_RKT_[_ZN4YAML4NodeixIA10_cEES0_RKT_]+0x34c): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/BattleItem.cpp.o:BattleItem.cpp:(.text+0x329f): more undefined references to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' follow
CMakeFiles/openxcom.dir/Savegame/BattleUnit.cpp.o: In function `OpenXcom::BattleUnitKills::load(YAML::Node const&)':
BattleUnit.cpp:(.text._ZN8OpenXcom15BattleUnitKills4loadERKN4YAML4NodeE[_ZN8OpenXcom15BattleUnitKills4loadERKN4YAML4NodeE]+0x589): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/BattleUnit.cpp.o: In function `YAML::Node& YAML::Node::operator=<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
BattleUnit.cpp:(.text._ZN4YAML4NodeaSINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEERS0_RKT_[_ZN4YAML4NodeaSINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEERS0_RKT_]+0x3a): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Country.cpp.o: In function `OpenXcom::Country::save() const':
Country.cpp:(.text+0x12a1): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Country.cpp:(.text+0x15d4): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Country.cpp:(.text+0x1954): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Country.cpp:(.text+0x1dbd): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Country.cpp.o:Country.cpp:(.text+0x24d0): more undefined references to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' follow
CMakeFiles/openxcom.dir/Savegame/SavedBattleGame.cpp.o: In function `YAML::Node::Scalar[abi:cxx11]() const [clone .isra.173]':
SavedBattleGame.cpp:(.text+0x359): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/SavedBattleGame.cpp.o: In function `OpenXcom::SavedBattleGame::save() const':
SavedBattleGame.cpp:(.text+0x4aa2): undefined reference to `YAML::EncodeBase64[abi:cxx11](unsigned char const*, unsigned int)'
CMakeFiles/openxcom.dir/Savegame/SavedBattleGame.cpp.o: In function `OpenXcom::SavedBattleGame::load(YAML::Node const&, OpenXcom::Mod*, OpenXcom::SavedGame*)':
SavedBattleGame.cpp:(.text+0x8925): undefined reference to `YAML::DecodeBase64(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/SavedGame.cpp.o: In function `YAML::Node::Scalar[abi:cxx11]() const [clone .isra.327]':
SavedGame.cpp:(.text+0x339): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/SavedGame.cpp.o: In function `OpenXcom::SavedGame::getSaveInfo(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, OpenXcom::Language*)':
SavedGame.cpp:(.text+0x4565): undefined reference to `YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/SavedGame.cpp.o: In function `OpenXcom::SavedGame::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const':
SavedGame.cpp:(.text+0x6653): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/SavedGame.cpp.o: In function `OpenXcom::SavedGame::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, OpenXcom::Mod*)':
SavedGame.cpp:(.text+0x9809): undefined reference to `YAML::LoadAllFromFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Soldier.cpp.o: In function `OpenXcom::Soldier::save() const':
Soldier.cpp:(.text+0x406c): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Soldier.cpp:(.text+0x4152): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Soldier.cpp:(.text+0x46ae): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/SoldierDiary.cpp.o: In function `YAML::Node::Scalar[abi:cxx11]() const [clone .isra.143]':
SoldierDiary.cpp:(.text+0x1e9): undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/openxcom.dir/Savegame/Target.cpp.o: In function `OpenXcom::Target::saveId() const':
Target.cpp:(.text+0x1d42): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Target.cpp:(.text+0x1dd5): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Target.cpp.o: In function `OpenXcom::Target::save() const':
Target.cpp:(.text+0x3311): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Target.cpp:(.text+0x33bc): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
Target.cpp:(.text+0x3721): undefined reference to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
CMakeFiles/openxcom.dir/Savegame/Target.cpp.o:Target.cpp:(.text+0x3a0b): more undefined references to `YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' follow
collect2: error: ld returned 1 exit status
src/CMakeFiles/openxcom.dir/build.make:7867: recipe for target 'bin/openxcom' failed
make[2]: *** [bin/openxcom] Error 1
CMakeFiles/Makefile2:90: recipe for target 'src/CMakeFiles/openxcom.dir/all' failed
make[1]: *** [src/CMakeFiles/openxcom.dir/all] Error 2
Makefile:136: recipe for target 'all' failed
make: *** [all] Error 2

Title: Re: Segmentation fault (core dumped) on starting
Post by: Yankes on June 14, 2016, 01:05:08 am

Its look like it try compile yaml statically. One solution could be adding yaml src to build system. It would probably resolve errors.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 14, 2016, 09:28:10 am

Quote from: Yankes on June 14, 2016, 01:05:08 am

Its look like it try compile yaml statically. One solution could be adding yaml src to build system. It would probably resolve errors.

I'll try on my own to do this, but I would be happy to get some more in depth instruction! I've gotten the source from here (https://archive.ubuntu.com/ubuntu/pool/universe/y/yaml-cpp/yaml-cpp_0.5.1-1.debian.tar.gz) and I've extracted it in .../oxce2.9-plus-proto/src/, but how do I add it to the build system?

Title: Re: Segmentation fault (core dumped) on starting
Post by: Yankes on June 14, 2016, 10:29:15 pm

This deepens on build tool you use, I usually use Makefile to build OXC.
In Makefile you need add lines:

Code: [Select]

SRCS_YAML = ../../lib/yaml-cpp/
SRCS_YAML_CPP = $(wildcard $(SRCS_YAML)src/*.cpp $(SRCS_YAML)src/contrib/*.cpp)

and

Code: [Select]

$(OBJDIR)yaml/%.o:: $(SRCS_YAML)src/%.cpp
	@mkdir -p $(OBJDIR)yaml
	$(CXX) $(CXXFLAGS) -c -o $@ $<

$(OBJDIR)yaml/%.o:: $(SRCS_YAML)src/contrib/%.cpp
	@mkdir -p $(OBJDIR)yaml
$(CXX) $(CXXFLAGS) -c -o $@ $<

Its shodul placed it like in https://github.com/Yankes/OpenXcom/blob/OpenXcomExtended/src/Makefile.mingw but this file is for Windows
Proper Makefile for linux is https://github.com/Yankes/OpenXcom/blob/OpenXcomExtended/src/Makefile.simple but build yaml dynamically from system headers.
You would need add this lines to it and remove yam from `$(shell $(PKG-CONFIG) --libs sdl yaml-cpp)`.

For cmake it will be probably bit harder, I don't know it how properly do it but fast hack would be adding manually new parts to https://github.com/Yankes/OpenXcom/blob/OpenXcomExtended/src/CMakeLists.txt

Code: [Select]

set ( yaml_src
  yaml/SomeYamlFile.cpp
  yaml/AnotherYamlFile.cpp
)

You will need probably list all cpp files manually to made it work (similar how rest of oxc is handled). Maybe is possible to use wild char like `*` to skip listing all files but I don't know without some googling.

Title: Re: Segmentation fault (core dumped) on starting
Post by: buenaventura on June 15, 2016, 03:32:25 pm

Thank you, that is very thorough! I will start trying this soon.

OpenXcom Forum

OpenXcom => Troubleshooting => Topic started by: buenaventura on June 10, 2016, 10:19:44 am