• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Breakpoints Being Ignored
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Breakpoints Being Ignored


  • Subject: Re: Breakpoints Being Ignored
  • From: Michael Monscheuer <email@hidden>
  • Date: Tue, 25 Nov 2003 06:25:15 +0100

Hey funny, I spent the weekend with a similar problem

Do you use XCode?
First thing to remember is, that XCode in some cases seems to ignore changes of target options and for that does not recompile all according stuff after you applied the changes.
So try "clean all" after you changed target options.

Of course you have to set this funny @executable_path/../Frameworks to INSTALL_PATH on Build tab of your Framework target - if framework shall be used as an embedded Framework.
See Chapter 27 you'll find in the book "Cocoa Programming"

I managed to step into Framework sourcecode during debugging.
Additionally I am now able to use the Framework with my dynamically loaded PlugIns together with the main program.
To gain this, I am using two copy rules within my main program target:
One copies the compiled Framework into the application bundle and another one copies the Framework into the build/MyProgram.build folder.
I added the Framework stored within build/MyProgram.build folder to my project via "Add Frameworks". Remember to avoid adding your framework to the framework target again
Add framework to main programms' target (and others) as a direct dependency.

I've read, that because of dynamic binding each module within a framework (do not mess the term "module" with "PlugIn"!) is bound dynamically to my dynamically loaded PlugIn Classes.
Dynamically binding means, that a needed module of the framework is bound to others first time you call it.
Here raises another problem, which took me a night:
The very first message sent to a dynamically bounded framework module cannot be traced. You can set a breakpoint or try to reach the module by a "step into". It just does not work. BUT: After the first message the module has been bounded and breakpoints and step into's do work again!
So after all I added some kind of activation class method to my framework for debugging purposes, which calls each (or a specific) module once. Then I added a message to this new framework class method within my PlugIns' +initialize method.
Strange, but works quite well...

I really have no idea, if this all works with PB...

Does this help you in some way?

MiMo


--
=======================================================
And refashioning the fashioned
lest it stiffen into iron
is work of endless vital activity.
[Goethe]

mailto:email@hidden
mailto:email@hidden

All about CALAMUS DTP suite:
http://www.calamus.net

=======================================================
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: NSSize not found in XCode
  • Next by Date: Getting called by the run loop
  • Previous by thread: Re: Stupid question: Flood Fill
  • Next by thread: Getting called by the run loop
  • Index(es):
    • Date
    • Thread