Re: Variable evaluating improperly
Re: Variable evaluating improperly
- Subject: Re: Variable evaluating improperly
- From: Jeffrey Walton <email@hidden>
- Date: Mon, 29 Apr 2013 20:19:12 -0400
On Mon, Apr 29, 2013 at 7:51 PM, Sean McBride <email@hidden> wrote:
> On Mon, 29 Apr 2013 16:28:50 -0600, koko said:
>
>>A picture is worth a thousands words:
>>
>>http://highrolls.net/What.png
>>
>>
>>You se the variable be DGProduct in the the variables display with a
>>values of 0.
>>
>>You se the current location in the source which should only be possible
>>if DGProduct != 0.
>>
>>What could possibly be the problem?
>
> This happens to me very often with boolean values. The debugger lies and say it's false when true, or vice verse. My bug is <rdar://12816285>, which is 'closed' because Apple is unable to reproduce. Not sure why, I see it every single day. :( If you have a repro case, please send it to them.
>
Apple's Debug Information settings are 'DWARF' and 'DWARF with dSYM'.
Both use '-g', which is equivalent to -g2'.
-g3 will often give you better result. At -g3, even symbolic defines
and macros are recorded in the debug information. To change to -g3,
add it to 'Other C Flags'.
There are lots of opportunities to set up a project more appropriately
for both Debug and Release. Some of them are discussed at
https://www.owasp.org/index.php/C-Based_Toolchain_Hardening. There's a
radar filed to have Apple include some of them in the iOS and Mac OS X
default schemes (Radar 12941954).
Jeff
_______________________________________________
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