> See above regarding looking at patches, but I guess you mean
> that the patch is trivial, so then I presume it was more or less
> the same as this, which is basically a copy-paste from looking
> at rs6000 and xtensa. I checked a typical /proc/self/maps and
> guess that 1<<29 probably fits for MI
2018-03-03 21:14 GMT+08:00 Hans-Peter Nilsson :
> > From: Jean Lee
> > Date: Fri, 2 Mar 2018 13:29:39 +0800
>
> > 2018-03-02 7:53 GMT+08:00 Hans-Peter Nilsson <
> hans-peter.nils...@axis.com>:
> >
> > > There's no address-sanitizer support f
2018-03-02 7:53 GMT+08:00 Hans-Peter Nilsson :
> There's no address-sanitizer support for MIPS (in particular for
> O32) on trunk, at least not when building for
> mipsisa32r2el-linux-gnu and libsanitizer/configure.tgt seems
> to support that observation. There's a set of patches "floating
> arou
I have tried Jakub patch listed in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58543.
It works for my env.
Thanks.
2013/10/29 Jean Lee :
> Thanks. I will try Jakub patch listed in
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58543.
>
> 2013/10/29 Yury Gribov :
>>> &qu
Thanks. I will try Jakub patch listed in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58543.
2013/10/29 Yury Gribov :
>> "copy_to_mode_reg (Pmode, XEXP (shadow_mem, 0))" would be more direct.
>> But it looks good to me with that change FWIW.
>
> Thanks, Richard. Note that Jakub has proposed an opti
Hi Yury, try to use the patch for asan.c to see if it solve your problem.
pinskia, thank you. I compiled asan with libssp which mean the stack grows down.
I disassembled the compiled code and debuged the bin time to time
before I thought it was a bug.early this month.
I tried GCC 4.8.1 and GCC 4.9
anks,
Jean Lee
2013/10/28 :
>
>> On Oct 28, 2013, at 1:36 AM, Jean Lee wrote:
>>
>> My port of addresssanitizer is based on GCC 4.8.1.
>> I modify "asan_emit_stack_protection" function in gcc/asan.c for the
>> following reason:
>> Sometimes, the
My port of addresssanitizer is based on GCC 4.8.1.
I modify "asan_emit_stack_protection" function in gcc/asan.c for the
following reason:
Sometimes, the stack variable size > 32 Bytes, and after asan
generates code to poison the shadow buffer, it does clear some shadow
buffer but not all before fu
