llvm dev - Mar 2017 - How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64

LLVM3.8 version.

https://bugs.llvm.org//show_bug.cgi?id=24233. The example can catch exception.
But I use my own code for testing, CustomEHMemoryManager allocated memory
address is very large, allocateCodeSection, allocateDataSection assigned address
(more than 32 bit address space) is getting smaller and smaller. Cause
registerEHFrames to fail.
3.9.1 or 4.0.0 version has been supported on win x64? Or how to solve this
problem?




haifeng.qin at wellintech.com
 
发件人： haifeng.qin at wellintech.com
发送时间： 2017-02-17 10:38
收件人： llvm-dev
主题： 回复: How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
I'm sorry。
I make mistakes. SE can be catched.



haifeng.qin at wellintech.com
 
发件人： haifeng.qin at wellintech.com
发送时间： 2017-02-16 17:48
收件人： llvm-dev
主题： How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
For help:
Llvm generated instruction calls a function (extern), the function will have a
SEH exception (EXCEPTION_ACCESS_VIOLATION),  But JIT can not capture the
exception of the EXCEPTION_ACCESS_VIOLATION. I saw Bug 24233.
EXCEPTION_ACCESS_VIOLATION exception cannot be captured after modification.

How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64 ?



haifeng.qin at wellintech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170227/0dfa3aaf/attachment.html>

I would not expect you to be able to catch any exceptions originating from
code JITed by LLVM on Win64. Nobody has implemented the code to register
the unwind data necessary to do this. The linked bug describes the steps
necessary to implement this functionality.

On Mon, Feb 27, 2017 at 12:34 AM, haifeng.qin at wellintech.com via llvm-dev
<
llvm-dev at lists.llvm.org> wrote:
> LLVM3.8 version.
>
> https://bugs.llvm.org//show_bug.cgi?id=24233. The example
> can catch exception. But I use my own code for testing,
> CustomEHMemoryManager allocated memory address is very large,
> allocateCodeSection, allocateDataSection assigned
> address (more than 32 bit address space) is getting
> smaller and smaller. Cause registerEHFrames to fail.
> 3.9.1 or 4.0.0 version has been supported on win x64? Or
> how to solve this problem?
>
>
> ------------------------------
> haifeng.qin at wellintech.com
>
>
> *发件人：* haifeng.qin at wellintech.com
> *发送时间：* 2017-02-17 10:38
> *收件人：* llvm-dev <llvm-dev at lists.llvm.org>
> *主题：* 回复: How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
> I'm sorry。
> I make mistakes. SE can be catched.
>
> ------------------------------
> haifeng.qin at wellintech.com
>
>
> *发件人：* haifeng.qin at wellintech.com
> *发送时间：* 2017-02-16 17:48
> *收件人：* llvm-dev <llvm-dev at lists.llvm.org>
> *主题：* How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
> For help:
> Llvm generated instruction calls a function (extern),
> the function will have a SEH exception (EXCEPTION_ACCESS_VIOLATION),  But
> JIT can not capture the exception of the EXCEPTION_
> ACCESS_VIOLATION. I saw Bug 24233. EXCEPTION_ACCESS_
> VIOLATION exception cannot be captured after modification.
>
> How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64 ?
>
> ------------------------------
> haifeng.qin at wellintech.com
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170301/9691ddaf/attachment.html>

Thank you for your reply. 

Can the function be implemented by exception handling
instructions(http://llvm.org/docs/ExceptionHandling.html#id34)?



haifeng.qin at wellintech.com
 
From: Reid Kleckner
Date: 2017-03-02 02:20
To: haifeng.qin at wellintech.com
CC: llvm-dev
Subject: Re: [llvm-dev] How to catch EXCEPTION_ACCESS_VIOLATION exceptions on
win64
I would not expect you to be able to catch any exceptions originating from code
JITed by LLVM on Win64. Nobody has implemented the code to register the unwind
data necessary to do this. The linked bug describes the steps necessary to
implement this functionality.

On Mon, Feb 27, 2017 at 12:34 AM, haifeng.qin at wellintech.com via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
LLVM3.8 version.

https://bugs.llvm.org//show_bug.cgi?id=24233. The example can catch exception.
But I use my own code for testing, CustomEHMemoryManager allocated memory
address is very large, allocateCodeSection, allocateDataSection assigned address
(more than 32 bit address space) is getting smaller and smaller. Cause
registerEHFrames to fail.
3.9.1 or 4.0.0 version has been supported on win x64? Or how to solve this
problem?




haifeng.qin at wellintech.com
 
发件人： haifeng.qin at wellintech.com
发送时间： 2017-02-17 10:38
收件人： llvm-dev
主题： 回复: How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
I'm sorry。
I make mistakes. SE can be catched.



haifeng.qin at wellintech.com
 
发件人： haifeng.qin at wellintech.com
发送时间： 2017-02-16 17:48
收件人： llvm-dev
主题： How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64
For help:
Llvm generated instruction calls a function (extern), the function will have a
SEH exception (EXCEPTION_ACCESS_VIOLATION),  But JIT can not capture the
exception of the EXCEPTION_ACCESS_VIOLATION. I saw Bug 24233.
EXCEPTION_ACCESS_VIOLATION exception cannot be captured after modification.

How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64 ?



haifeng.qin at wellintech.com

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170306/e2c271ff/attachment.html>