similar to: [LLVMdev] exception handling bug?

Hello, > #1 0x00000033fc810c66 in _Unwind_RaiseException () from /lib64/libgcc_s.so.1 > #2 0x00000033fd4c3dbd in __cxa_throw () from /usr/lib64/libstdc++.so.6 What's your native gcc version? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Anton Korobeynikov wrote: > Hello, > >> #1 0x00000033fc810c66 in _Unwind_RaiseException () from >> #/lib64/libgcc_s.so.1 >> #2 0x00000033fd4c3dbd in __cxa_throw () from /usr/lib64/libstdc++.so.6 > What's your native gcc version? > gcc-4.3.0-8.x86_64

Can you point out to me where in the VMKit code I should be looking? I spent some additional time reading the docs, and I have some specific questions: 1) I'm trying to figure out the relationship between the __cxa_throw function, and the _Unwind_RaiseException function mentioned in the ABI doc. My guess is that _Unwind_RaiseException is the language-neutral implementation of stack unwinding,

Hi Talin, > 1) I'm trying to figure out the relationship between the __cxa_throw > function, and the _Unwind_RaiseException function mentioned in the ABI doc. > My guess is that _Unwind_RaiseException is the language-neutral > implementation of stack unwinding, and __cxa_throw is the C++ exception > semantics that are implemented on top of it. If that is the case, should I >

Hi Talin, Talin wrote: > After much delay, I have finally reached the point in my work where I > need to implement some kind of exception handling. I understand that > "unwind" is currently unimplemented and will remain so for the > forseeable future. > > In the mean time, are there any examples available for implementing Java > or Python-style exceptions using

After much delay, I have finally reached the point in my work where I need to implement some kind of exception handling. I understand that "unwind" is currently unimplemented and will remain so for the forseeable future. In the mean time, are there any examples available for implementing Java or Python-style exceptions using __cxa_throw or something similar? I've read and

I'm trying to add some basic exception handling to my language now and I'm uncertain of how I actually start the exception propagation. It appears that "resume" will continue the exception, but I see no mention of how the exception actually starts. If I look at the IR output of a simple C++ program I see that it calls @__cxa_throw, but that is a library function. Somehow I must

On 29 Mar 2013, at 17:15, edA-qa mort-ora-y <eda-qa at disemia.com> wrote: > I'm trying to add some basic exception handling to my language now and > I'm uncertain of how I actually start the exception propagation. It > appears that "resume" will continue the exception, but I see no mention > of how the exception actually starts. > > If I look at the IR

2009/6/15 Török Edwin <edwintorok at gmail.com>: > Write some C++ code into llvm.org/demo, and watch the output assembly, That shows how to use the c++ runtime for handling c++ style exceptions. More useful might be an llvm implementation of __cxa_throw, which I could then modify. ;)

On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > Just want to remind everyone that we plan to stop using mach_override in > asanin favor of OSX's native function interposition. > So, we probably don't want to spend too much effort fixing mach_override. > > --kcc Kostya, Is the native function interposition that is being adopted based on...

Looks like this happens on x86_64 because the position of __cxa_throw is too far from the allocated branch island (should be <2G). This can be solved by allocating the branch islands somewhere near the text segment (look for kIslandEnd in asan_mac.cc, this is currently 0x7fffffdf0000) or by patching the function with a longer instruction sequence that stores the jump target in a register and

Just want to remind everyone that we plan to stop using mach_override in asanin favor of OSX's native function interposition. So, we probably don't want to spend too much effort fixing mach_override. --kcc On Fri, Nov 30, 2012 at 4:46 AM, Alexander Potapenko <glider at google.com>wrote: > Looks like this happens on x86_64 because the position of __cxa_throw > is too far from

Hi Duncan, >>are you trying to get the name "@_ZTIi" or "@__cxa_throw"? yes! i want get the name @_ZTi or @__cxa_throw, the latter @__cxa_throw i can get it throw value->getName(), but the @_ZTi it did n't has name! zhangzw thanks 2009/3/26 Duncan Sands <baldrick at free.fr>: > Hi zhangzw, > >> invoke void @__cxa_throw(i8* %7, i8*

I debugged this a bit and it seems the mach_override patching of __cxa_throw is bogus. The start of that function is patched to jump to garbage. Breakpoint 1, 0x0000000100001c19 in main () (gdb) display/i $pc 2: x/i $pc 0x100001c19 <main+318>: callq 0x100016386 <dyld_stub___cxa_throw> (gdb) si 0x0000000100016386 in dyld_stub___cxa_throw () 2: x/i $pc 0x100016386

Hey Duncan, Yup, you are correct. Just tested to make sure. Invoking _Unwind_RaiseException(...) directly still sets up personality function (and calls it during exception search/cleanup), in corresponding frame headers for frame containing invoke. Well ... ok, at least in a JIT execution environment. :-) I thought maybe __gcc_personality_v0(...) was being called instead. However, I also just

Sorry to have to ask... I'm catching too much noise from dumps. I'm building LLVM 7.0 using release tarballs on OS X 10.5 PowerPC. I'm building out-of-tree mostly following https://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary . Cmake gets this far and hangs: -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Looking

On Sat, Dec 01, 2012 at 05:42:15PM +0400, Kostya Serebryany wrote: > +kremenek, ganna > > On Sat, Dec 1, 2012 at 4:33 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > > > On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > > > Just want to remind everyone that we plan to stop using mach_override in > > > asanin favor of OSX's

Hi James, Looking at: %7 = invoke i8* (...)* bitcast (i32 (%struct._Unwind_Exception*)* @_Unwind_RaiseException to i8* (...)*)(i64* %6) to label %8 unwind label %.finally_pad ; <i8*> [#uses=0] I am not sure this is going to work, at least from the way I've played with the system. In my examples the _Unwind_RaiseException(...) is called from a frame (function) called via

+kremenek, ganna On Sat, Dec 1, 2012 at 4:33 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > > Just want to remind everyone that we plan to stop using mach_override in > > asanin favor of OSX's native function interposition. > > So, we probably don't want to spend too much effort fixing

Hi zhangzw, >> invoke void @__cxa_throw(i8* %7, i8* bitcast >> (%struct.__fundamental_type_info_pseudo* @_ZTIi to i8*), void (i8*)* >> null) >> noreturn to label %invcont unwind label %lpad > > >>are you trying to get the name "@_ZTIi" or "@__cxa_throw"? > > yes! i want get the name @_ZTi or @__cxa_throw, > the latter