Re: Question about increasing error checking during development builds
Re: Question about increasing error checking during development builds
- Subject: Re: Question about increasing error checking during development builds
- From: "Sean McBride" <email@hidden>
- Date: Thu, 10 Jan 2008 17:46:55 -0500
- Organization: Rogue Research
On 1/10/08 2:30 PM, Jayson Adams said:
>I'm using Xcode 2.4.1 on Tiger. When I compile my app for
>deployment, I sometimes get warnings about potentially uninitialized
>variables, but I don't get these warnings when I compile for
>development. Does anyone know how I can tweak my development build
>settings so that I get this extra level of error checking when I do
>development builds?
By searching the gcc man page for "uninitialized" one finds:
"-Wuninitialized
Warn if an automatic variable is used without first being initialized or
if a variable may be clobbered by a "setjmp" call.
These warnings are possible only in optimizing compilation, because they
require data flow information that is computed only when optimizing. If
you don't specify -O, you simply won't get these warnings."
And you probably don't want to turn on optimizations in Debug, you'll
just have to build release once in a while to check for all warnings.
--
____________________________________________________________
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