Re: GDB: Timed out fetching data
Re: GDB: Timed out fetching data
- Subject: Re: GDB: Timed out fetching data
- From: Jim Ingham <email@hidden>
- Date: Fri, 19 Nov 2010 09:20:09 -0800
On Nov 19, 2010, at 5:52 AM, Kevin Meaney wrote:
> Hi,
>
> I have been having trouble in Xcode 3.2.3 with GDB.
>
> We have a very large project and development occurs on Leopard with Xcode 3.1.3 and in that environment everything works fine. We did initially have some problems with debugging (many years ago) but turning off load symbols lazily in the preferences plus switching to DWARF debugging when that became available fixed the problems.
>
> I have recently bought myself a new laptop (10.6 and Xcode 3.2.3) and was trying to do some debugging last night at home, but that was effectively skuppered by debugging being broken. I kept getting the message "Timed out fetching data" and the debugger locking up. Googling managed to find some reports of this issue and that it can be fixed by turning off the data formatters. This worked but it is a poor solution as most of the information I need for debugging is no longer available.
>
> I have looked at the notes for the update of Xcode to version 3.2.4 and there is nothing there that suggests a fix for this particular problem. I have a copy of the gdb log if anybody would like to see.
The answer to this is always yes. Please file a report at bugreport.apple.com.
In cases where running DataFormatters is hanging the debug session, it is also useful to get a sample of the application you are debugging. These hangs usually happen because the data formatter needs to run some code in your program's address space and when we do that we try to run only the thread into which we've injected this call. But sometimes that can cause deadlocks against other threads in the program. Seeing a sample of your program will help us determine if that is the case.
Another reason we can sometimes hang up is when a data formatter is run on an object that hasn't been initialized yet. We try to detect this, since feeding bad objects to the runtime can cause various bad behavior - including hangs in the ObjC runtime. There was a bug introduced in 3.2.3 which caused us to miss some cases where the object was bad. We fixed that in 3.2.4, so you might want to give that a try and see if it works better for you.
Jim
>
> Does anybody have a solution?
>
> Kevin
>
> _______________________________________________
> 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