• 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, gdb and "Timed out fetching data"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode, gdb and "Timed out fetching data"


  • Subject: Re: XCode, gdb and "Timed out fetching data"
  • From: Scott F Bayes <email@hidden>
  • Date: Thu, 22 Mar 2007 10:02:12 +0900

Many thanks to all for the responses!

I think Jim has described my situation: formatters timing out on uninit-ed objects, especially stringy things. I'll muck with the settings, find the workarounds that work for me, maybe po, or init- ing everything in the local context before the breakpoint when I can.

Scott

On Mar 22, 2007, at 00:40 , Jim Ingham wrote:

This generally means that some one of the "data formatters" is taking too long to return. You can verify this by turning OFF the data formatters with the Debug->Variables View->Enable Data Formatters menu item.

Some of the data types in Cocoa & Carbon - the string types & the collection types particularly - are opaque to the debugger, so to tell you their values we have to call some code in the program we are debugging. This can go wrong in numerous ways, most of which we intercept & deal with. But not all yet...

One common cause of problems is trying to run the data formatters on uninitialized objects. We don't actually have any way to tell for sure when an object is good or not. We have some heuristics, but stack objects sometimes point to the leftovers of another stack object that are "almost good enough" and fool us. One trick that will help out with this is when you are breaking in a function, break after the objects are initialized, not at the very beginning of the function.

Or, you can just leave the data formatters off, and use "po" or the "Print object" context-menu in the variable view to look at ObjC objects.

Jim


On Mar 21, 2007, at 5:07 AM, Scott F Bayes wrote:

Briefly, when trying to use XCode 2.4.1 on 10.4.8 (or 9) to debug a little Cocoa app that started life in IB and has had very little added since then, I get the following message in the Debugger, and gdb becomes sullen and won't do anything useful after that till I kill it and start a new debug run:

	GDB: Timed out fetching data. Variable display may be inaccurate.




_______________________________________________ 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: 
 >XCode, gdb and "Timed out fetching data" (From: Scott F Bayes <email@hidden>)
 >Re: XCode, gdb and "Timed out fetching data" (From: Jim Ingham <email@hidden>)

  • Prev by Date: Universal mock objects?
  • Next by Date: Redux: App launched in Xcode can't gain key and order front
  • Previous by thread: Re: XCode, gdb and "Timed out fetching data"
  • Next by thread: multi-key bindings in Xcode?
  • Index(es):
    • Date
    • Thread