Re: XCode, gdb and "Timed out fetching data"
Re: XCode, gdb and "Timed out fetching data"
- Subject: Re: XCode, gdb and "Timed out fetching data"
- From: Jonas Maebe <email@hidden>
- Date: Thu, 22 Mar 2007 15:42:47 +0100
On 22 mrt 2007, at 15:24, Sean McBride wrote:
On 3/21/07 10:55 AM, Jim Ingham said:
Not that I know of. Not sure this is the best solution, however:
adding another way that debug builds run differently from optimized
builds doesn't seem desirable.
Yeah, I see your point. I guess I was thinking of it as an extra,
like
guard malloc. If all stack variables were inited to 0, it would make
unintentional reliance on their initial value behave consistently.
Actually, initialising to a non-zero (but defined) value is much
better in general. The reason is that (in my experience) most errors
which suddenly pop up because of uninitialised variables weren't
detected earlier exactly because they were accidentally zero.
I've added an option to our (Pascal) compiler to trash all local
variables at the start of the block they are declared in (you can
choose from 4 pre-defined values), and it has helped already several
times with finding errors which were hard to reproduce otherwise
(like "can't reproduce when running inside the debugger").
Jonas
_______________________________________________
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