[llvm-commits] [PATCH] AddressSanitizer Initialization Order Checking

Reid Watson reidw at google.com
Fri Jul 13 10:02:20 PDT 2012


Kostya,

I completely missed that (caught in a poorly written email filter).
Thanks for reviewing it for me, and I'll use rietveld when submitting
the update d version.
I'm looking at the code now, and I'll update when I've implemented the
suggested changes.

--Reid

On Fri, Jul 13, 2012 at 4:41 AM, Kostya Serebryany <kcc at google.com> wrote:
> Reid,
>
> Have you seen my replies to your previous patches?
> http://comments.gmane.org/gmane.comp.compilers.clang.scm/53381
> http://permalink.gmane.org/gmane.comp.compilers.llvm.cvs/116782
>
> --kcc
>
> On Thu, Jul 12, 2012 at 9:19 PM, Reid Watson <reidw at google.com> wrote:
>>
>> Hello,
>>
>> Attached are two patches which add support for detecting
>> initialization order problems in AddressSanitizer.
>> Issues with initialization order are checked by poisoning the shadow
>> memory of global variables which are not guaranteed to have been
>> initialized before each modules initializers run.
>> This approach catches the most obvious issues with initialization
>> order, and correctly ignores access to global variables which should
>> be accessible during initializers (function local statics, etc.).
>>
>> All the best,
>> Reid
>>
>> _______________________________________________
>> llvm-commits mailing list
>> llvm-commits at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>>
>



More information about the llvm-commits mailing list