DunbarXX Posted April 8, 2009 Share Posted April 8, 2009 Hello All! Recently I installed iDeneb 1.4 (MacOSX Leo 10.5.6) My PC is an AMD Athlon64 X2 with 2GB of RAM. I installed the latest iPhone dev kit (2.2.1) and created a simple iPhone application project. The project was build successfully and iPhone simulator started and executed the application. Then I decided that I need to debug it to trace the code to see what happens. I put a breakpoint in the main loop and it wouldnt break the execution. I tried everything, loading symbols non lazily, playing with different project settings but none seems to work. I start the project with attached debugger and nothing happens. I wonder if the problem is in my CPU or I need to do something to make the debugger stop? Please if you have any suggestion how to resolve this problem share it with me! Thank you!!! Xcode ver is: 3.1.2 Here is the output in the Debugger Console [session started at 2009-04-08 22:46:08 +0300.]Loading program into debugger… GNU gdb 6.3.50-20050815 (Apple version gdb-962) (Sat Jul 26 08:14:40 UTC 2008) 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-apple-darwin".warning: Unable to read symbols for "/System/Library/Frameworks/UIKit.framework/UIKit" (file not found). warning: Unable to read symbols from "UIKit" (not yet mapped into memory). warning: Unable to read symbols for "/System/Library/Frameworks/OpenGLES.framework/OpenGLES" (file not found). warning: Unable to read symbols from "OpenGLES" (not yet mapped into memory). Program loaded. sharedlibrary apply-load-rules all Attaching to program: `/Users/cocococov/Library/Application Support/iPhone Simulator/User/Applications/B7A73432-7446-4246-93C0-9596EC7B33C4/First.app/First', process 441. Re-enabling shared library breakpoint 1 Previous frame inner to this frame (gdb could not unwind past this frame) Previous frame inner to this frame (gdb could not unwind past this frame) (gdb) continue Previous frame inner to this frame (gdb could not unwind past this frame) Previous frame inner to this frame (gdb could not unwind past this frame) (gdb) continue Link to comment Share on other sites More sharing options...
pontifex22 Posted April 18, 2009 Share Posted April 18, 2009 I had these problems too. It is Voodoo kernel related. It's on their bug list. I don't know when they will fix it, so I switched from my former perfect running AMD setup to a brand new E7400 Core 2 Duo. Even better. Link to comment Share on other sites More sharing options...
DunbarXX Posted April 22, 2009 Author Share Posted April 22, 2009 Thank you pontifex22. I thought that may be the reason too! After all MacOS is not made to run on AMD's Link to comment Share on other sites More sharing options...
PolishOX Posted April 23, 2009 Share Posted April 23, 2009 You can try this boot argument but I was only able to get it working with INTEL hacks: std_dyld=1 -v Link to comment Share on other sites More sharing options...
Recommended Posts