Re: Enabling AddressSanitizer from Xcode
Re: Enabling AddressSanitizer from Xcode
- Subject: Re: Enabling AddressSanitizer from Xcode
- From: Jeffrey Walton <email@hidden>
- Date: Thu, 14 Mar 2013 16:28:12 -0400
On Thu, Mar 14, 2013 at 2:06 PM, Sean McBride <email@hidden> wrote:
> On Thu, 14 Mar 2013 01:03:47 -0400, Jeff Smith said:
>
>>Since AddressSanitizer is part of LLVM/Clang, is it possible to enable
>>it from Xcode's Build Settings?
>
> No. Apple uses their own fork of clang for Xcode, which does not include the Asan work google did. File a bug and wait forever (you can dupe mine <rdar://11056201>). In the mean time, build your own clang and point Xcode to it:
> <http://blog.wadetregaskis.com/tot-clang-llvm-in-xcode/>
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) and -fsanitzie=memory? Its an open question for me,
so I thought I would ask.
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.
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.
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