Re: GCC 4.0 compiled code behaves differently with Debug on
Re: GCC 4.0 compiled code behaves differently with Debug on
- Subject: Re: GCC 4.0 compiled code behaves differently with Debug on
- From: Scott Ribe <email@hidden>
- Date: Tue, 27 Dec 2005 09:15:50 -0700
- Thread-topic: GCC 4.0 compiled code behaves differently with Debug on
> Their values might not be
> zero, but when they are compiled with Debug, those variable are now
> automatically initialized to zero, and the problem goes away.
Well, there's all sorts of other memory bugs that can cause debug and
release builds to behave differently, or bugs to disappear when you add
logging functions. Any time you change the code, you change layout in
memory. Therefore, if you have some bug that is corrupting memory, you can
change what is getting corrupted, from something important to something
unused, or vice versa.
I really wouldn't suspect the compiler here. I would suspect writing through
a dangling pointer, or beyond array bounds.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
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