Re: Xcode 3.2.2 Re-enabling shared library breakpoint
Re: Xcode 3.2.2 Re-enabling shared library breakpoint
- Subject: Re: Xcode 3.2.2 Re-enabling shared library breakpoint
- From: Nivek Research <email@hidden>
- Date: Mon, 26 Apr 2010 00:38:05 -0400
Hi Jeff,
"Modify the Build Products Path setting for both the application and framework targets so that they use the same build directory. You need to modify each target in their original Xcode project file."
I modified the framework project to build in a separate build products directory (contrary to the documentation) and now I do not get the messages from GDB and the breakpoints all work. Thanks very much for the pointer. --kevin
On Apr 25, 2010, at 9:49 PM, Jeff Johnson wrote: Hi Kevin. Yes, I've experienced the same problem. This seems to be a regression in Xcode 3.2.2, does not occur in 3.2.1. I've filed a bug: rdar://problem/7898146 Xcode 3.2.2 REGRESSION: can't debug embedded framework What's the structure of your app and Xcode project? As far as I can tell, the problem only occurs if the framework/library is built in the same directory as the app and is also embedded in the app. A workaround is to delete the built copy of the library in the build directory before debugging. -Jeff On Apr 25, 2010, at 8:04 PM, Nivek Research wrote: I did a clean install of Xcode 3.2.2 from the xcode322_2148_developerdvd.dmg (downloaded from the developer connection) on a Mac OS X v10.6.3 system. Now I get messages stating "Re-enabling shared library breakpoint #" flooding the GDB console. Worse the debugger never breaks at any of the breakpoints listed. Anyone else experiencing this problem? Anyone know how to silence the messages and make breakpoints work in shared libraries?
--kevin
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden