1.11.5 can't get campaigns to run
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
1.11.5 can't get campaigns to run
as reported here: https://gna.org/bugs/?20951
Anyone else having this problem? I built from source using make- re-downloaded the source and tried again, no dice. I am running wesnoth from the terminal. 1.11.4 works fine, built/ran the same way.
Anyone else having this problem? I built from source using make- re-downloaded the source and tried again, no dice. I am running wesnoth from the terminal. 1.11.4 works fine, built/ran the same way.
Re: 1.11.5 can't get campaigns to run
So the bug report is yours? Do you have any add-ons installed? Could you list them?
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
Re: 1.11.5 can't get campaigns to run
Yep that's my report- I removed all of the addons, and I just now deleted the entire 1.11 folder that contains the addons and tried running wesnoth again, it still just hangs.
terminal output is identical when starting 1.11.5 and 1.11.4
terminal output is identical when starting 1.11.5 and 1.11.4
Re: 1.11.5 can't get campaigns to run
Note that anonymissimus asked you to attach the --log-debug=all output (the full output) in the tracker and you haven’t done so yet. Just the last line generally won’t suffice to diagnose a problem.Crow_T wrote:terminal output is identical when starting 1.11.5 and 1.11.4
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
Re: 1.11.5 can't get campaigns to run
Is there a more elegant way to do this? There are so many lines generated that the top part is getting cut off (I'm no terminal expert). I'm getting this repeated a lot though:
If this means nothing I'll try again tomorrow using gnome terminal or find a better one somewhere...
Code: Select all
The config object has no child named »filter«.
20130717 20:33:26 debug config: The config object has no child named »filter_vision«.
20130717 20:33:26 debug config: The config object has no child named »filter_adjacent_location«.
20130717 20:33:26 debug config: The config object has no child named »filter_owner«.
Re: 1.11.5 can't get campaigns to run
Crow_T wrote:Is there a more elegant way to do this?
Code: Select all
$ wesnoth --log-debug=all 2> path/to/output_file.txt
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
Re: 1.11.5 can't get campaigns to run
OK, huge txt file is up at the bug tracker, thanks for the tips.
Re: 1.11.5 can't get campaigns to run
the problem described in this thread sounds similar:
http://forums.wesnoth.org/viewtopic.php ... 25#p544425
http://forums.wesnoth.org/viewtopic.php ... 25#p544425
Re: 1.11.5 can't get campaigns to run
Well Max, you found the answer- building with scons instead of make worked. Thanks!
Re: 1.11.5 can't get campaigns to run
If you have time, could you runCrow_T wrote:Well Max, you found the answer- building with scons instead of make worked. Thanks!
make clean
, then make VERBOSE=1
and record the full command line printed on the screen for each .cpp file? (Yes, that’s a rebuild using the cmake configuration.) You can use make | tee logfile.txt
to record the output to logfile.txt in the current directory automatically. Additionally, I’d also want to see the scons build log as it appears during the scons build, what compiler you are using, and what version it is (e.g. the output of gcc --version
for GCC).(The point is that there is an issue that is most likely linked to the compiler option set used by the cmake recipe, so if we want to look into it we need to know the environment conditions that trigger it.)
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
Re: 1.11.5 can't get campaigns to run
From bug #20951 [Gna.org], for whoever might want to help us understand this bug better:
shadowm wrote:Since the reporter seems to not be interested in providing additional information in the forums [1], I'm posting this here as well.
[1] http://forums.wesnoth.org/viewtopic.php ... 70#p557270
I would suspect that there's a problem with compiler optimizations at work here. If my memory serves, the default used with scons is -O2, whereas cmake uses -O3 for Release builds. I personally use -O3 -march=native with scons here, running gcc version 4.7.2 and a full amd64 Debian wheezy system, and I have not seen anything like this so far with 1.11.x or 1.10.x. From what I read, Ubuntu 13.04 (raring)'s default is gcc 4.7.3 [2]. I expect that both the Debian wheezy and raring gcc packages include additional patches that could have something to do with this bug.
[2] http://packages.ubuntu.com/raring/gcc
Additionally, a gdb backtrace would be very helpful.
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
Re: 1.11.5 can't get campaigns to run
If this is a simple one step thing I can try I can give it a shot. I've been out of the loop because of some real life things, but if you guys could put the commands into a format that I ould copy/paste that would help a lot. I don't code so I'm not really familiar with build environments. The GCC version that I have installed is 4.7.3Additionally, a gdb backtrace would be very helpful.
Is anyone else having this problem btw?
Re: 1.11.5 can't get campaigns to run
You would need to make sure you have gdb installed in your package manager, and use cmake to produce a faulty Wesnoth build again. What I said above about gathering more information during the build still applies, but you may just provide a copy of the CMakeCache.txt file from the build dir instead.Crow_T wrote:If this is a simple one step thing I can try I can give it a shot.
Then, load Wesnoth on gdb on a terminal emulator window. The following will load the Wesnoth binary named ./path/to/wesnoth, redirect stderr to stdout, and record stdout in a file named debug-session-log.txt in the current directory.
Code: Select all
$ gdb ./path/to/wesnoth 2>&1 | tee debug-session-log.txt
Code: Select all
(gdb) start
Code: Select all
(gdb) bt
Code: Select all
(gdb) q
(I have just realized that cmake by default (well, cmake 2.8.9, anyway) doesn’t use the Release build type, so unless you specified a build type or optimization level explicitly, it should be the compiler default of -O0 — which only raises more questions. Hence I want to see either CMakeCache.txt or the actual compiler command line in
`make VERBOSE=1`
.)Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.