CPU Killer, Segfault Thriller.

Where bugs go to lie down and rest

Moderator: Moderator

Post Reply
Message
Author
metaspike
Posts: 3
Joined: Thu Jan 19, 2012 12:07 pm

CPU Killer, Segfault Thriller.

#1 Post by metaspike »

Hi there, I would like to say that I am very impressed with t-engine 4 and the tome game, despite the following issues. fyi I am running debian amd64 on a 2.4ghz 2core system using fglrx with a hd5670. The recompiled binary runs smoothly except it is using 100% of either core at anytime and about 30% of the other. If i limit the CPU usage with "cpulimit" to say, 80%, the program becomes 20% laggier. Something is definitely amiss here. It would be great if there was someway to reduce more effective layers for troubleshooting / frugal purposes. I managed to compile from source but it segfaults after "make wait background" displaying a box which tries to resize and then vanishes. I hope this information helps with the development of ToME.

svn build run log: http://pastebin.com/Mw9M5Kia

precompiled binary run log: http://pastebin.com/pfXY9bLks

Rectifier
Archmage
Posts: 386
Joined: Mon Aug 29, 2011 8:06 am

Re: CPU Killer, Segfault Thriller.

#2 Post by Rectifier »

Since this is linux this is mostly beyond my knowledge, but here is my log from b37, perhaps you can use this to see where/what is going wrong on the svn.
http://pastebin.com/FSf0fqjZ

I noticed that your log was asking for pulseaudio.c, pcm.c, and pcm_dmix.c but couldn't find them, are those files in your svn's src folder or open al's include folder? If neither is true, find them and put them in the src folder, and if the files exist in open al's include, put a copy of the al's include folder into the svn src folder as well and see if that helps. And by that I mean copy the yourdir\include\AL folder's contents, not the folder itself, and paste them into yourdir\tome\src . Also you might have to re-compile.

metaspike
Posts: 3
Joined: Thu Jan 19, 2012 12:07 pm

Re: CPU Killer, Segfault Thriller.

#3 Post by metaspike »

thanks for your suggestion, i think i've figured out the cause of the problem with gdb.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7258e13 in IMG_LoadPNG_RW ()
from /usr/lib/x86_64-linux-gnu/libSDL_image-1.2.so.0

so... what now? :) maybe if I knew what versions I should be compiling this with. maybe i'll scrounge through the compiler once more and see if i've missed something. maybe i've returned to dependency hell!

Post Reply