Page 1 of 1

Issue about Startup Crash of STK, compiled on Mac OSX 1.6

PostPosted: 08 Aug 2012, 11:48
by Klinux
Hey guys,

When I first successfully compiled the source, I thought I made it.

But after awhile, opps, Program received signal "EXC_BAD_ACCESS"...

the information from GDB:

a lot of warnings such as
...
{l Code}: {l Select All Code}
warning: Could not find object file "/Users/mmg/Desktop/fribidi/build/fribidi.build/Release/fribidi.build/Objects-normal/i386/fribidi-char-sets.o" - no debug information available for "/Developer/libs/fribidi-0.19.2/charset/fribidi-char-sets.c".


after "run"

{l Code}: {l Select All Code}
.++++++................................................................................................... done
Irrlicht Engine version 1.8.0-alpha
Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
Reading symbols for shared libraries . done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000044
0x00beddb7 in irr::core::string<char, irr::core::irrAllocator<char> >::operator= ()


For the code, I directly downloaded it from the home page, not svn, since it seems there are something wrong with the Xcode Project file. And also I installed irrlicht r3843.

after a long time searching and jumping among different forums, I still cannot fix the problem, so can anybody help me out of this?

Thanks a lot..

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 08 Aug 2012, 23:39
by Auria
Hi,

in gdb, when you reach the point where it crashed, please enter the 'bt' command (without quotes) to get a backtrace

Now you seem to mention you installed irrlicht yourself. The build system of STK on OSX pretty much assumes that you will be using the official dependency pack, so I'm not sure what happens when you install irrlicht yourself in a separate location. This error could be a mismatch between the versions of the irrlicht headers used and the irrlicht library linked in, though with a backtrace I would be more sure

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 09 Aug 2012, 20:06
by Klinux
Thanks for the reply Auria,
for the info after type bt in gdb:
{l Code}: {l Select All Code}
(gdb) bt
#0  0x00beddb7 in irr::core::string<char, irr::core::irrAllocator<char> >::operator= ()
#1  0x00d83423 in irr::io::CFileSystem::changeWorkingDirectoryTo ()
#2  0x0013ace2 in FileManager::FileManager (this=0x142bee0, argv=0xbffff8d4) at /Users/Klinux/Desktop/supertuxkart-0.7.3/src/ide/Xcode/../../io/file_manager.cpp:141
#3  0x000d406e in initUserConfig (argv=0xbffff8d4) at /Users/Klinux/Desktop/supertuxkart-0.7.3/src/ide/Xcode/../../main.cpp:957
#4  0x000d7c49 in main () at /Users/Klinux/Desktop/supertuxkart-0.7.3/src/ide/Xcode/../../main.cpp:1106


actually, to install irrlicht r3843 is the most suggested solution that I found, when I compile the project with official dependency and a lot errors came out.

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 09 Aug 2012, 21:34
by Klinux
And I also tried to compile it by using cmake, and link errors:
{l Code}: {l Select All Code}
[100%] Building CXX object CMakeFiles/supertuxkart.dir/src/utils/vec3.cpp.o
Linking CXX executable bin/supertuxkart.app/Contents/MacOS/supertuxkart
ld: framework not found IrrFramework
collect2: ld returned 1 exit status
make[2]: *** [bin/supertuxkart.app/Contents/MacOS/supertuxkart] Error 1
make[1]: *** [CMakeFiles/supertuxkart.dir/all] Error 2
make: *** [all] Error 2

further
{l Code}: {l Select All Code}
Linking CXX executable bin/supertuxkart.app/Contents/MacOS/supertuxkart
ln: /Users/Klinux/Desktop/stk-trunk/cmake_build/bin/supertuxkart.app/Contents/Resources/data: File exists
make[2]: *** [bin/supertuxkart.app/Contents/MacOS/supertuxkart] Error 1
make[1]: *** [CMakeFiles/supertuxkart.dir/all] Error 2
make: *** [all] Error 2

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 11 Aug 2012, 01:11
by Auria
ld: framework not found IrrFramework


hmm you did download the dependency pack, and install the frameworks inside it? this should have placed a folder called IrrFramework.framework in /<hard disk>/Library/Frameworks. Check if this file does exist?

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 11 Aug 2012, 08:49
by Klinux
Sure, at beginning, I followed the steps on the official website using cmake, but it doesn't work.. so I try to compile it in other way.

for the Frameworks I installed:

{l Code}: {l Select All Code}
pptp-212-201-77-59:~ Klinux$ cd /Library/Frameworks/

pptp-212-201-77-59:Frameworks Klinux$ ls
AEProfiling.framework      Ogg.framework         iLifeFaceRecognition.framework
AERegistration.framework   OpenAL.framework      iLifeKit.framework
AudioMixEngine.framework   PluginManager.framework      iLifePageLayout.framework
HPSmartPrint.framework      Vorbis.framework      iLifeSQLAccess.framework
IrrFramework.framework      cisco-vpnclient.framework   iLifeSlideshow.framework
NyxAudioAnalysis.framework   fribidi.framework      iTunesLibrary.framework

pptp-212-201-77-59:Frameworks Klinux$ cd IrrFramework.framework/
pptp-212-201-77-59:IrrFramework.framework Klinux$ ls
Headers      IrrFramework   Versions
pptp-212-201-77-59:IrrFramework.framework Klinux$


Thanks.

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 12 Aug 2012, 02:28
by Auria
Unfortunately I just tested building with CMake on my OSX 10.6 system and it all worked out of the box, so I'm not sure what is different for you :( can you check if the symlinks (aliases) inside the framework are ok? that's the only thing that comes to my mind

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 12 Aug 2012, 15:13
by Klinux
Hi Auria, actually, after that I tried a clean compiling, and it works now. Thank you and thanks for your patient.

Re: Issue about Startup Crash of STK, compiled on Mac OSX 1.

PostPosted: 12 Aug 2012, 17:00
by Auria
Klinux {l Wrote}:Hi Auria, actually, after that I tried a clean compiling, and it works now. Thank you and thanks for your patient.


ah ok, glad that it works now :)