• 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 debugger & NSString display
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode debugger & NSString display


  • Subject: Re: Xcode debugger & NSString display
  • From: Han Ming Ong <email@hidden>
  • Date: Mon, 09 Dec 2013 09:19:04 -0800


On Dec 8, 2013, at 4:53 PM, Peter Teeson <email@hidden> wrote:


On 2013-12-08, at 6:17 PM, Fritz Anderson wrote:
On 8 Dec 2013, at 2:43 PM, Peter Teeson <email@hidden> wrote:

My environment: OS X Lion 10.7.5, Xcode 4.6.3
I have Googled, and StackOverFlowed but not yet found what can be done.


... [The Debugger IDE doesn't show the contents of immutable strings in the Variables pane, even though they show up in the lldb console] ...

Questions

(0) Did I miss something?
(1) How can this be solved to display the data for _NSCFConstantStrings?

I hope somebody has experience to draw on to help you, but I fear many people would say this: 

The best way to address a bug in software that is one major version back, running on an operating system two major versions back, is to use current versions of both. Back then, especially, lldb and Xcode were "improving rapidly," which is a euphemism for "even the immediately previous version is unusable compared to the latest."


Thats a fair enough comment. So does the Debugger IDE show the contents of immutable strings in Xcode 5.xx? 
If not then moving to Xcode 5 and either Mountain Lion or Mavericks won't solve that issue will it.
(I have ML but haven't moved to it yet; for what I wish to do it's not required)

I’m pretty sure it does. That seems like a bad bug that should have been squashed already.

You may not know this but you can actually run multiple versions of Xcode nowadays, since they can ‘co-exist’. That allows you to try out latest, with the latest bug fixes etc, and fall back to your previous version if necessary. Sometimes there may be a upgrade of the project model (may not be intentional) so if you want to be safe, you should back up your project when trying out the new Xcode.

I personally find that it is more manageable to do incremental upgrade than to do a big jump in Xcode versions. YMMV.

Han Ming
ps: I just tested on latest Xcode, your problem is indeed solved.
 _______________________________________________
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 debugger & NSString display
      • From: Peter Teeson <email@hidden>
References: 
 >Xcode debugger & NSString display (From: Peter Teeson <email@hidden>)
 >Re: Xcode debugger & NSString display (From: Fritz Anderson <email@hidden>)
 >Re: Xcode debugger & NSString display (From: Peter Teeson <email@hidden>)

  • Prev by Date: Re: Xcode 5 Core Data mapping model editor can't drag-rearrange items?!
  • Next by Date: Where to look for the replacement for a deprecated API?
  • Previous by thread: Re: Xcode debugger & NSString display
  • Next by thread: Re: Xcode debugger & NSString display
  • Index(es):
    • Date
    • Thread