Displaying 4 results from an estimated 4 matches for "unwi".
Did you mean:
uni
2017 May 01
1
Possible stack corruption during call to JITSymbol::getAddress()
...ory smashing. ORC is
currently failing to deregister the EH-frame section when the JIT is torn
down (but *is* deallocating the memory for it). Normally that's not
disastrous (though it does leave bogus EH frames in memory), but in your
case the thrown exception tears down the JIT itself, so the unwinder ends
up reading eh-frames that have been deallocated. I'm working on a fix to
have the JIT properly deregister EH frames, but one workaround for now
would be to make sure you catch the exception before it causes the JIT
stack to be destructed.
Cheers,
Lang.
On Thu, Apr 20, 2017 at 9:42 AM...
2017 Apr 20
2
Possible stack corruption during call to JITSymbol::getAddress()
...gt;>>
>>>> Basically, I have a reproduction case (below) where if I throw an
>>>> exception before I call JITSymbol::getAddress() everything works properly
>>>> but throwing the same exception afterward will result in a SIGSEGV during
>>>> stack unwinding. This suggests to me that somehow the stack is getting
>>>> corrupted during the JITSymbol::getAddress() call.
>>>>
>>>> This problem was initially discovered while working on my own project.
>>>> While troubleshooting this I've discvoered t...
2017 Apr 17
2
Possible stack corruption during call to JITSymbol::getAddress()
...;s so little there about LLVM ORC.
>>
>> Basically, I have a reproduction case (below) where if I throw an
>> exception before I call JITSymbol::getAddress() everything works properly
>> but throwing the same exception afterward will result in a SIGSEGV during
>> stack unwinding. This suggests to me that somehow the stack is getting
>> corrupted during the JITSymbol::getAddress() call.
>>
>> This problem was initially discovered while working on my own project.
>> While troubleshooting this I've discvoered that when LLVM is
>> -DLLVM...
2017 Apr 09
2
Possible stack corruption during call to JITSymbol::getAddress()
...e the correct place
for this since there's so little there about LLVM ORC.
Basically, I have a reproduction case (below) where if I throw an exception
before I call JITSymbol::getAddress() everything works properly but
throwing the same exception afterward will result in a SIGSEGV during stack
unwinding. This suggests to me that somehow the stack is getting corrupted
during the JITSymbol::getAddress() call.
This problem was initially discovered while working on my own project.
While troubleshooting this I've discvoered that when LLVM is
-DLLVM_USE_SANITIZER:STRING=Address the problem ha...