• 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: String display problems on iPad
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: String display problems on iPad


  • Subject: Re: String display problems on iPad
  • From: Han Ming Ong <email@hidden>
  • Date: Sat, 5 Feb 2011 13:39:53 -0800

Well, to run data formatters, gdb has to run code inside your application and that has serious implications, including deadlocking or crashing your debugging app.
I can reasonably guess that with 3.2, gdb is more careful (in consultation with the runtime) to know if it can run data formatters at the very instant that you show data tip. And if the runtime says 'sorry, no go', gdb has to not run the formatters...

To be sure though, please file a bug with the gdb log attached (so that we can do an audit over it). Of course, we could display a better string message instead of the actual formatter string (bonus point for that bug too).

thanks, Han Ming

On Feb 5, 2011, at 1:19 PM, Jerry porter wrote:

> Sorry forgot the URL
> http://stackoverflow.com/questions/1427871/xcode-3-2-debug-seeing-whats-in-an-array
>
> Sent from my iPad
>
> On Feb 5, 2011, at 16:00, Jerry porter <email@hidden> wrote:
>
>> Here is a blog post that might help.
>> I have not tried it myself
>>
>> Sent from my iPad
>>
>> On Feb 4, 2011, at 14:53, Gordon Apple <email@hidden> wrote:
>>
>>> Why can't the XCode debugger display strings in the variable summary area
>>> when running debug on the iPad? Instead, I get gobbledegook like "{(char
>>> *)Xcode_CFStringSummary($VAR, $ID)}:s".  Not very useful.
>>>
>>> I'm trying to debug some font issues.  It works properly on the simulator.
>>> Also the following does not give me info on the fontNames array (like number
>>> of elements):
>>>
>>>  NSArray* fontFamilyNames = [UIFont familyNames];
>>>  for(NSString* ffName in fontFamilyNames) {
>>>      NSArray* fontNames = [UIFont fontNamesForFamilyName:ffName];
>>>      NSUInteger idx = [fontNames indexOfObject:name];
>>>      if(idx != NSNotFound)
>>>          return YES;
>>>  }
>>>
>>> Is the debugger just that lame when debugging on the device?  Or have I
>>> missed some settings somewhere?
>>>
>>>
>>> _______________________________________________
>>> 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
>> _______________________________________________
>> 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
> _______________________________________________
> 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

 _______________________________________________
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

References: 
 >String display problems on iPad (From: Gordon Apple <email@hidden>)
 >Re: String display problems on iPad (From: Jerry porter <email@hidden>)
 >Re: String display problems on iPad (From: Jerry porter <email@hidden>)

  • Prev by Date: Re: String display problems on iPad
  • Next by Date: Re: String display problems on iPad
  • Previous by thread: Re: String display problems on iPad
  • Next by thread: Re: String display problems on iPad
  • Index(es):
    • Date
    • Thread