Re: Enabling AddressSanitizer from Xcode
Re: Enabling AddressSanitizer from Xcode
- Subject: Re: Enabling AddressSanitizer from Xcode
- From: Sean McBride <email@hidden>
- Date: Thu, 14 Mar 2013 16:35:55 -0400
- Organization: Rogue Research Inc.
On Thu, 14 Mar 2013 16:28:12 -0400, Jeffrey Walton said:
>Hi Sean. I agree with you about the bug reporting and waiting. Its
>frustrating at times.
:)
>In this case, what is the difference between the stuff Apple makes
>available through Schemes -> Diagnostics (Memory Edge, Malloc and
>Scribble guards)
Those have been around forever, and are part of the malloc implementation. See 'man malloc' in the 'ENVIRONMENT' section, and see 'man libgmalloc'.
>and -fsanitzie=memory? Its an open question for me,
>so I thought I would ask.
-fsanitzie=memory is 'Not ready for widespread use', see:
<http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation>
>Related: some of the other -fsanitize=xxx looks *absolutely* bad ass
>(http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation).
>I can't wait to get my grubby pawls on them. I see Peng Li and John
>Regehr's IOC made it in via -fsanitize=shift and
>-fsanitize=signed-integer-overflow.
Yes, they are great. I've been running them for a few months now, slowly fixing the hundreds of bugs they have found in my code and open source code I use.
>I'd also like to see something added for the 'implementation defined'
>behavior being abused in the string functions, such as passing NULL to
>strcmp.
Static analyzer warns about this, but of course that's not the same as a runtime check.
Cheers,
--
____________________________________________________________
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