Displaying 3 results from an estimated 3 matches for "full_view".
2012 Jun 08
0
[LLVMdev] Windows C++ ABI: Reverse Engineering Articles (FYI)
This is only of interest to those who are working on implementing support
for the Microsoft Visual C++ ABI:
http://www.openrce.org/articles/full_view/21
http://www.openrce.org/articles/full_view/23
The first details the implementation of Microsoft's exception handling,
whereas the other looks at classes, methods, and RTTI.
Cheers,
Mikael
-- Love Thy Frog!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <...
2016 Jun 10
2
Windows: How to catch C++ exceptions in runtime-compiled code?
...hen entering the function between the two cases, static- vs. runtime-compiled, turns out that pThrowInfo points to nulled memory in the runtime-compiled case, while it has some data in the static-compiled case. Detailed information about the types can be found here: http://www.openrce.org/articles/full_view/21 <http://www.openrce.org/articles/full_view/21>. Most likely the "attributes" and "pCatchableTypeArray" members are required for RaiseException to resolve the correct catch pad?
To find out why the ThrowInfo structure is empty in the runtime-compiled case, we compared w...
2016 Oct 24
2
RuntimeDyLdCOFF and RTTI on Windows
I have a similar build tree to what you describe on Windows, but I get this:
$ clang -c -emit-llvm repro_input.cpp -std=c++11 -o t.bc
$ lli t.bc
LLVM ERROR: Program used external function '??_7type_info@@6B@' which could
not be resolved!
It looks like people have already reported similar issues. Have you done
anything to get past this kind of problem?
On Sat, Oct 22, 2016 at 7:18 AM,