• 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: Xcode 2.1 debugger grief
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.1 debugger grief


  • Subject: Re: Xcode 2.1 debugger grief
  • From: Ricky Sharp <email@hidden>
  • Date: Fri, 10 Jun 2005 23:19:34 -0500


On Jun 8, 2005, at 7:36 PM, Chris Espinosa wrote:

You didn't say what you upgraded *from*. If you came from gcc3.3 to gcc4.0, or from Panther to Tiger, there are underlying OS and compiler changes that might explain this.

Originally, a custom IBPalette and app were both built with gcc3.3 (This was back when I was using Xcode 1.5 running on Mac OS X 10.3.x).



As a starting point last night, I went down the path of reconstructing the my app project slowly. But alas, same grief. This led me to believe that the problem was most likely in my code.


I think I've narrowed things down to my custom IB palette code (and corresponding custom classes) and their use of custom bindings.

I just compiled my IBPalette with Xcode 2.1, but left the target at 10.3 and SDK at 10.3.9. Compiles up a-ok, but if I bring up the bindings inspector pane on any of my widgets, IB will either crash right there and then, or crash when I quit the app.

And, because the widget code is being used in my app, it now makes sense that things are hosed if my bindings stuff is doing something truly evil. The apps use my custom bindings everywhere and I first noticed the strange results with those widgets that are bound. Unbound widgets seem to work a-ok.

So the root difference here is indeed the switch from gcc3.3 to 4.0.

More work ahead, but at least I have something to go on!

Hmm... one area that may be of concern is lines of code like this:

static void* MinimumValueBindingIdentifier = (void*) @"IIValueFieldMinimumValue";

This sets up a unique identifier for a custom binding which is passed as the context parameter to addObserver:forKeyPath:options:context:

That param is typed to be void*, but perhaps the declaration above is doing something bad when compiled with gcc4.0? I will play with this tomorrow.


___________________________________________________________ Ricky A. Sharp mailto:email@hidden Instant Interactive(tm) http://www.instantinteractive.com

_______________________________________________
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


  • Follow-Ups:
    • Re: Xcode 2.1 debugger grief [Solved]
      • From: Ricky Sharp <email@hidden>
References: 
 >Xcode 2.1 debugger grief (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.1 debugger grief (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.1 debugger grief (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: prebind warnings on 10.4 XCode 2.1 SDK 10.4u
  • Next by Date: Re: Xcode 2.1 dependency problems.
  • Previous by thread: Re: Xcode 2.1 debugger grief
  • Next by thread: Re: Xcode 2.1 debugger grief [Solved]
  • Index(es):
    • Date
    • Thread