I just installed The Mana World (0.0.16) with absolutely no errors coming up during the make/make install process. However, when I typed "tmw" at the terminal to start the game I was given an error:
[root@cpe-61-65-287-126 tmw-0.0.16]# tmw
Fatal signal: Segmentation Fault (SDL Parachute Deployed)
I've deleted the files installed and done a remake, etc. but the same thing continues to plague me. Here are my system details:
OS: Fedora Core 4
SDL: 1.2.8
SDL_mixer: 1.2.6
SDL_image: 1.2.4
Physfs: 1.0.0
As for libxml2 and zlib, I have them, but I'm unsure of the version numbers. I've also tried installing with the OpenGL option, but that proved to have the same fate.
Help is appreciated.
Crash on startup
Crash on startup
Last edited by BHensley on 09 Oct 2005, 13:07, edited 1 time in total.
No, it doesn't. I tried the gdb, but it returns "No stack."
[root@cpe-55-55-55-55 tmw-0.0.16]# gdb /usr/local/bin/tmw
GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) bt
No stack.
-
ElvenProgrammer
- Founder
- Posts: 2526
- Joined: 13 Apr 2004, 19:11
- Location: Italy
- Contact:
TMW Italian communityIf I run tmw through the terminal then no window displays. However, if I run it from the KMenu a window does appear, but closes very quickly and before any image is loaded (stays black).ElvenProgrammer wrote:The window doesn't even display?
It created the log file? If so can you show the content of it?
Try to run with the --skipupdate option.
Where would the log be found? Not sure if it created one, nothing's in my root directory, and no log files are in the TMW directory (/usr/local/share/tmw).
I ran tmw with the --skipupdate, but to no avail. From both the terminal and the menu, the same exact thing happens.
Odd, now I'm receiving a different error.
And, here's my log:[root@cpe-55-55-55-55 ~]# /usr/local/share/tmw/data/tmw
Error: Couldn't load login_wallpaper.png
All of the images noted in the log do exist, have appropriate permissions (rw-r--r--), and don't seem to be corrupted at all (I can view them in Konqueror).[22:02:09] Using video driver: x11
[22:02:09] Possible to create hardware surfaces: no
[22:02:09] Window manager available: yes
[22:02:09] Accelerated hardware to hardware blits: no
[22:02:09] Accelerated hardware to hardware colorkey blits: no
[22:02:09] Accelerated hardware to hardware alpha blits: no
[22:02:09] Accelerated software to hardware blits: no
[22:02:09] Accelerated software to hardware colorkey blits: no
[22:02:09] Accelerated software to hardware alpha blits: no
[22:02:09] Accelerated color fills: no
[22:02:09] Available video memory: 0
[22:02:09] ResourceManager::get(graphics/images/login_wallpaper.png)
[22:02:09] Error, image load failed
[22:02:09] ResourceManager::get(graphics/sprites/player_male_base.png)
[22:02:09] Error, image load failed
[22:02:09] ResourceManager::get(graphics/sprites/player_male_hair.png)
[22:02:09] Error, image load failed
[22:02:09] Error: Couldn't load login_wallpaper.png
[22:02:09] Sound::close() Shutting down sound...
1. I didn't specify a prefix, I kept the default (so, /usr/local/share I'd assume)maci wrote:seems very lot like a problem with paths
a few questions.
what prefixes did you use for compiling tmw?
from what dir did you start tmw ?
where are all the tmw related files are actually located?
2. Assuming you mean the directory my terminal was changed to when typing the "tmw" command -> ~. Though, I did a cd to /usr/local/share/tmw/data, and did "tmw" again, same thing.
3. /usr/local/share/tmw
-
Bjørn
- Manasource
- Posts: 1438
- Joined: 09 Dec 2004, 18:50
- Location: North Rhine-Westphalia, Germany
- Contact:
There is no stack because you didn't run the program, which you'd need to do using "run". You'd only use "bt" when the program actually crashed.BHensley wrote:I tried the gdb, but it returns "No stack."
[root@cpe-55-55-55-55 tmw-0.0.16]# gdb /usr/local/bin/tmw
GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) bt
No stack.
Anyway the image load failed error could also be related to libpng support missing from SDL_image or something. I know a lot (all?) of Slackware users had this problem.