Displaying 4 results from an estimated 4 matches for "runerror".
2009 Mar 10
4
[LLVMdev] C++ Exception Handling Problem
...nctions. There are
already try/catch blocks in place in the C++ function that calls the JITted
functions.
The problem I run into is that when exceptions are thrown, they aren't
caught anywhere. My program crashes with an error message: "terminate called
after throwing an instance of 'RunError'". Where RunError is the exception
type. Hence, the exceptions aren't getting caught where they should be.
What I'd like to know is how I can fix this situation, so that if my C++
runtime support functions throw an exception, it can unwind the JITted
functions properly, and these...
2009 Mar 10
0
[LLVMdev] C++ Exception Handling Problem
...y try/catch blocks in place in the C++ function that calls the JITted
> functions.
>
> The problem I run into is that when exceptions are thrown, they aren't
> caught anywhere. My program crashes with an error message: "terminate called
> after throwing an instance of 'RunError'". Where RunError is the exception
> type. Hence, the exceptions aren't getting caught where they should be.
does this happen in the non-jit context. For example, suppose rather than
JITing your bitcode you compile it down to object code, and arrange for it
to be called from C++ a...
2009 Mar 10
0
[LLVMdev] C++ Exception Handling Problem
...dy try/catch blocks in place in the C++ function that calls the JITted
> functions.
>
> The problem I run into is that when exceptions are thrown, they aren't
> caught anywhere. My program crashes with an error message: "terminate called
> after throwing an instance of 'RunError'". Where RunError is the exception
> type. Hence, the exceptions aren't getting caught where they should be.
>
> What I'd like to know is how I can fix this situation, so that if my C++
> runtime support functions throw an exception, it can unwind the JITted
> functi...
2009 Mar 10
2
[LLVMdev] C++ Exception Handling Problem
...function that calls the
>> JITted
>> functions.
>>
>> The problem I run into is that when exceptions are thrown, they aren't
>> caught anywhere. My program crashes with an error message: "terminate
>> called
>> after throwing an instance of 'RunError'". Where RunError is the
>> exception
>> type. Hence, the exceptions aren't getting caught where they should be.
>
> does this happen in the non-jit context. For example, suppose rather than
> JITing your bitcode you compile it down to object code, and arrange fo...