Displaying 4 results from an estimated 4 matches for "402ed8".
Did you mean:
402ed5
2011 Jun 17
3
[LLVMdev] LLVM-based address sanity checker
...es a call to run-time).
It generates more code, it also creates prologue/epilogue in otherwise leaf
functions.
Such mode may still be useful if for whatever reason we can not use SIGILL.
Default (use ud2):
402ed5: 48 89 d8 mov %rbx,%rax << move the
address to rax
402ed8: 0f 0b ud2a << crash
402eda: 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 d...
2011 Jun 21
0
[LLVMdev] LLVM-based address sanity checker
...re code, it also creates prologue/epilogue in otherwise leaf
> functions.
> Such mode may still be useful if for whatever reason we can not use
> SIGILL.
>
> Default (use ud2):
> 402ed5: 48 89 d8 mov %rbx,%rax << move the
> address to rax
> 402ed8: 0f 0b ud2a << crash
> 402eda: 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...
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