Re: Timed out fetching data...
Re: Timed out fetching data...
- Subject: Re: Timed out fetching data...
- From: Dix Lorenz <email@hidden>
- Date: Sun, 12 Sep 2004 08:37:44 +0200
On 11.09.2004, at 15:05, Rainer Brockerhoff wrote:
At 11:17 +0200 11/09/2004, Thomas Lachand-Robert wrote:
Le 10 sept. 04, ` 22:51, Rainer Brockerhoff a icrit :
I found that this may happen when variables are declared further
along in a function or method and a breakpoint is set before their
initialization. Moving all declarations to the front like in the old
days and making sure all pointers are initialized to nil will
usually fix it.
Not anymore. It ued to be the case in XCode 1.2 (maybe due to the
version of gdb), but now in XCode 1.5 this has been very well
corrected: if you set a breakpoint in the code before the declaration
of some variable, it displays "out of scope". So there is no more any
reason to predeclare the variables (which is a very bad practive
anyway, a door wide open to bugs).
I've never seen this on 1.2. In my experience, depending on what
garbage pointers may contain, "Timed out fetching data" only happens
on 1.5 and apparently _before_ displaying the "out of scope" message.
Not usually, but sometimes. Predeclaring _always_ fixes it for me,
although I don't like it either...
I had that problem in 1.2 and I still have it in 1.5. I do not intend
to rewrite hundreds of tested, legal and correct functions (and
probably introducing bugs) only to work around a definite bug in some
tool. I have filed a bug (of course) and included my idea of why this
would occur. I used the console to print out one instance of one of my
simpler (C++) classes. This recursed into each member variable and
some of the "deeper" classes have lots of static constants. All this
got printed out, resulting in 9781 lines. "First level"-variables (the
ones I am mostly interested in) only would have taken up 4 lines. I
have another class which comes out at 21000 lines and one at 86000
lines! As far as I understand it the Debugger asks gdb to print the
variables, then reads the result, parses it and then displays it. Those
are literally hundreds of thousands of lines and will take some time. I
don't know if that is the actual problem but since the error says
"timed out" it seems to make sense to me...
Dix
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden