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: "Sean McBride" <email@hidden>
- Date: Thu, 22 Mar 2007 10:24:46 -0400
- Organization: Rogue Research
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.
>
>Jim
>
>On Mar 21, 2007, at 10:35 AM, Sean McBride wrote:
>
>> On 3/21/07 8:40 AM, Jim Ingham said:
>>
>>> 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.
>>
>> Is there any way for stack variables to be automatically initialised
>> to
>> zero (or something) when debugging? I believe Visual Studio allows
>> this. That might help.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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