Ravenman Posted September 12, 2010 Report Share Posted September 12, 2010 Hi to everyone:I have one big problem: I'm trying to compile and run 0ad in my computer, but 0ad compiles with a lot of warnings and after does not run! The compilation process shows these messages in the console: (see the attached compile.txt file). The running process shows these messages in the console: (see the attached run0ad.txt file). What can I do? compile.txtrun0ad.txt Quote Link to comment Share on other sites More sharing options...
Ykkrosh Posted September 12, 2010 Report Share Posted September 12, 2010 What version of the game is this?Can you run it in a debugger? ("gdb /usr/bin/pyrogenesis", "r", wait for crash, "bt full") Quote Link to comment Share on other sites More sharing options...
Ravenman Posted September 12, 2010 Author Report Share Posted September 12, 2010 What version of the game is this?Can you run it in a debugger? ("gdb /usr/bin/pyrogenesis", "r", wait for crash, "bt full")This is the latest version: r07970 in Arch Linux system.This is the outcome from gdb:[user@archerpc ~]$ gdb /opt/0ad/system/pyrogenesis GNU gdb (GDB) 7.2Copyright (C) 2010 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. Type "show copying"and "show warranty" for details.This GDB was configured as "x86_64-unknown-linux-gnu".For bug reporting instructions, please see:<http://www.gnu.org/software/gdb/bugs/>...Reading symbols from /opt/0ad/system/pyrogenesis...done.(gdb) rStarting program: /opt/0ad/system/pyrogenesis [Thread debugging using libthread_db enabled]ERROR: Error initializing FAM; hotloading will be disabledTIMER| InitVfs: 5.36425 ms[New Thread 0x7ffff7ff8710 (LWP 3095)][New Thread 0x7fffec43f710 (LWP 3096)]TIMER| InitScripting: 725.74 usTIMER| CONFIG_Init: 2.32214 msTIMER| write_sys_info: 1.93597 msPerformance warning: your graphics card does not support compressed textures. The game will try to continue anyway, but may be slower than expected. Please try updating your graphics drivers; if that doesn't help, please try upgrading your hardware.TIMER| InitRenderer: 328.497 msTIMER| ps_console: 1.6314 msTIMER| ps_lang_hotkeys: 1.4252 msTIMER| common/setup.xml: 893.04 usTIMER| common/styles.xml: 275.587 usTIMER| common/sprite1.xml: 1.94887 msTIMER| common/init.xml: 1.66723 msTIMER| pregame/sprites.xml: 646.652 usTIMER| pregame/styles.xml: 113.394 usTIMER| pregame/mainmenu.xml: 8.23929 msTIMER| common/global.xml: 504.343 usTIMER| common/setup.xml: 484.363 usTIMER| common/styles.xml: 222.712 usTIMER| common/sprite1.xml: 1.89339 msTIMER| msgbox/msgbox.xml: 863.22 us[Thread 0x7ffff7ff8710 (LWP 3095) exited][New Thread 0x7ffff7ff8710 (LWP 3097)][Thread 0x7ffff7ff8710 (LWP 3097) exited][New Thread 0x7ffff7ff8710 (LWP 3098)]TIMER| common/setup.xml: 519.035 usTIMER| common/styles.xml: 219.764 usTIMER| common/sprite1.xml: 1.82453 msTIMER| gamesetup/setup.xml: 372.066 usTIMER| gamesetup/sprites.xml: 115.712 usTIMER| gamesetup/styles.xml: 136.3 usTIMER| gamesetup/gamesetup_mp.xml: 4.57322 ms[Thread 0x7ffff7ff8710 (LWP 3098) exited][New Thread 0x7ffff7ff8710 (LWP 3099)]TIMER| common/setup.xml: 553.983 usTIMER| common/styles.xml: 296.036 usTIMER| common/sprite1.xml: 1.99145 msTIMER| gamesetup/setup.xml: 82.559 usTIMER| gamesetup/sprites.xml: 51.449 usTIMER| gamesetup/styles.xml: 66.613 usTIMER| gamesetup/gamesetup.xml: 4.43206 ms[Thread 0x7ffff7ff8710 (LWP 3099) exited][New Thread 0x7ffff7ff8710 (LWP 3100)][Thread 0x7ffff7ff8710 (LWP 3100) exited][New Thread 0x7ffff7ff8710 (LWP 3101)]TIMER| common/setup.xml: 569.491 usTIMER| common/styles.xml: 286.61 usTIMER| common/sprite1.xml: 1.93573 msTIMER| common/init.xml: 1.66176 msTIMER| loading/loading.xml: 963.624 usTIMER| common/global.xml: 327.529 usTIMER| common/setup.xml: 577.34 usTIMER| common/styles.xml: 299.012 usTIMER| common/sprite1.xml: 1.89901 msTIMER| common/icon_sprites.xml: 5.62878 msTIMER| session_new/sprites.xml: 995.378 usTIMER| session_new/styles.xml: 224.682 usTIMER| session_new/session.xml: 37.7509 msTIMER| common/global.xml: 1.16057 ms[New Thread 0x7fffe64b3710 (LWP 3102)]SND| alc_init: success, using ALSA SoftwareGAME STARTED, ALL INIT COMPLETE[Thread 0x7ffff7ff8710 (LWP 3101) exited][New Thread 0x7ffff7ff8710 (LWP 3103)]Program received signal SIGSEGV, Segmentation fault.0x00007fffeb648296 in ?? () from /usr/lib/xorg/modules/dri/r600_dri.so(gdb) bt full#0 0x00007fffeb648296 in ?? () from /usr/lib/xorg/modules/dri/r600_dri.soNo symbol table info available.Cannot access memory at address 0x7fffffffda78(gdb) Quote Link to comment Share on other sites More sharing options...
Ykkrosh Posted September 12, 2010 Report Share Posted September 12, 2010 /usr/lib/xorg/modules/dri/r600_dri.so is the graphics driver, so it sounds like the bug is there. Several people have reported problems with the drivers for ATI hardware - I think they were fixed in later versions, so upgrading things like Mesa (maybe to a git snapshot, I don't know if it's in a stable release) might help. Otherwise you should probably report it as a driver bug. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.