Displaying 4 results from an estimated 4 matches for "__asan_report_error_2".
2011 Jun 17
3
[LLVMdev] LLVM-based address sanity checker
...a: 52 push %rdx << encode is_write
and size in the opcode
(note: with a good disassembler and some work we can leave just ud2 or
equivalent)
-mllvm -asan-use-call
402ed5: 48 89 df mov %rbx,%rdi << address is the
paremeter to __asan_report_error_2
402ed8: e8 53 69 00 00 callq 409830
<__asan_report_error_2> << is_write and size is encoded in the function
name
--kcc
>
>
> On 32-bit, the shadow region is:
>> [0x28000000, 0x3fffffff] HighShadow [0x24000000, 0x27ffffff] ShadowGap [0x20000000,
>...
2011 Jun 21
0
[LLVMdev] LLVM-based address sanity checker
...ush %rdx << encode
> is_write and size in the opcode
> (note: with a good disassembler and some work we can leave just ud2 or
> equivalent)
>
> -mllvm -asan-use-call
> 402ed5: 48 89 df mov %rbx,%rdi << address is the
> paremeter to __asan_report_error_2
> 402ed8: e8 53 69 00 00 callq 409830
> <__asan_report_error_2> << is_write and size is encoded in the function
> name
>
>
> --kcc
>
>
>>
>>
>> On 32-bit, the shadow region is:
>>> [0x28000000, 0x3fffffff] HighShado...
2011 Jun 17
0
[LLVMdev] LLVM-based address sanity checker
On 17 June 2011 09:14, Kostya Serebryany <kcc at google.com> wrote:
> Maybe the fallback code should just use a function call. Much simpler for
> documentation purposes.
Sounds good.
On 32-bit, the shadow region is:
> [0x28000000, 0x3fffffff] HighShadow [0x24000000, 0x27ffffff] ShadowGap [0x20000000,
> 0x23ffffff] LowShadow
>
> This is 0.5G total. So, I mmap all these
2011 Jun 17
3
[LLVMdev] LLVM-based address sanity checker
On Fri, Jun 17, 2011 at 12:04 PM, Renato Golin <rengolin at systemcall.org>wrote:
> On 17 June 2011 08:55, Kostya Serebryany <kcc at google.com> wrote:
> > I am rather reluctant to add 'generic' code that handles unknown/untested
> > platforms because the memory mapping is very platform specific anyway.
>
> Indeed, but the point of that is more for helping