search for: __register_frame

Hi, I had similar problems with EH in ELF in RTDyldMemoryManager::registerEHFrames() calling __register_frame(). I'm not sure these problems are related to this problem since your crash happens in RuntimeDyldMachO::registerEHFrames() in its own processFDE (there are two functions named processFDE(), one in RuntimeDyldMachO.cpp and one in RTDyldMemoryManager.cpp) *before* RTDyldMemoryManager::registe...

...for a couple of weeks. I'll bring it up to date and try my test case on it and we'll see what happens. Best, .Chris. Yaron Keren <yaron.keren at gmail.com> writes: > Hi, > > I had similar problems with EH in ELF in > RTDyldMemoryManager::registerEHFrames() calling __register_frame(). > > I'm not sure these problems are related to this problem since your > crash happens in  RuntimeDyldMachO::registerEHFrames() in its own > processFDE (there are two functions named processFDE(), one in > RuntimeDyldMachO.cpp and one in RTDyldMemoryManager.cpp) >  before R...

On 04/30/2013 11:53, Rafael Espíndola wrote: > Are you trying MCJIT?:-) No. > > I first tried to compensate for that in MCJIT by adding those 4 bytes. > That works for Linux, but not for OS X where __register_frame takes a > single FDE at a time. I have an incomplete wip patch if you are > interested. On BSD __register_frame also takes a single argument and therefore needs terminating zero. I also have a simple patch for this: adding Streamer.EmitIntValue(0, 4); at the end of MCDwarfFrameEmitter::Emi...

...support === Summary === # of expected passes 2727 # of unexpected failures 57 # of expected failures 6 The extra success test is funccall.ll from test/DebugInfo. In order to build successfully LLVM on ARM Linux EABI platform, I put in comment the usage of __register_frame into JIT.cpp because it seems that __register_frame function is not into my libgcc. Could you mention which tools and versions that must to be used in order to build LLVM on ARM Linux EABI platform. Thanks, Mikaël. http://www.nabble.com/file/p20938563/arm-debug-from-llvm2-4.patch arm-debug-from-...

.../13 23:42, Brian Herman wrote: > I got the following error while compiling llvm and clang under cygwin. > > /cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b): > undefined reference to `__register_frame' I register_frame is used to enable the debugger (gdb) to debug JIT'd code. It is a function provided by libgcc, to be more precise in libgcc_eh. Is it in your copy? $ nm libgcc_eh.a | grep register_fram 0000000000001960 T __deregister_frame 0000000000001950 T __deregister_frame_info 00...

...c: 3 to 00021524 DW_CFA_def_cfa_reg: r6 DW_CFA_nop DW_CFA_nop DW_CFA_nop You can see that the last section of .eh_frame begins at 0x2cb14 in file, and has 4 (size value DWORD)+0x18(data)=0x1C bytes. There is the string table immediately after .eh_frame. The problem with this is that __register_frame function (in libgcc_s.so), registering .eh_frame with an exception handler, only takes the pointer to .eh_frame, and not the size of data, and should be able to detect the end of data by scanning it and hitting zero DWORD (size). There is no trailing zero, and it runs into the next section and...

> The problem with this is that __register_frame function (in libgcc_s.so), > registering .eh_frame with an exception handler, only takes the pointer to > .eh_frame, and not the size of data, and should be able to detect the end of > data by scanning it and hitting zero DWORD (size). There is no trailing > zero, and it runs into the n...

I got the following error while compiling llvm and clang under cygwin. /cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b): undefined reference to `__register_frame' /cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `__register_frame' /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x...

Hi, There may be two problems with __register_frame usage. However based on http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061768.html I think the existing code is correct for OS-X but likely buggy for Linux and Windows systems. Your crash is on OS-X, right? Anyhow, the first problem is very easy to fix. On Linux and Windows (at least) _...

Hi, all I come across the problem when building llvm. The errors are as follows ... etJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': : undefined reference to `__register_frame' collect2: ld returned 1 exit status make[2]: *** [/home/lishengmei/llvm-2.6/Release/bin/lli] Error 1 make[2]: Leaving directory `/home/lishengmei/llvm-2.6/tools/lli' make[1]: *** [lli/.makeall] Error 2 make[1]: Leaving directory `/home/lishengmei/llvm-2.6/tools' make: *** [all] E...

...f expected passes 2727 > # of unexpected failures 57 > # of expected failures 6 > > The extra success test is funccall.ll from test/DebugInfo. In order > to build > successfully LLVM on ARM Linux EABI platform, I put in comment the > usage of > __register_frame into JIT.cpp because it seems that __register_frame > function is not into my libgcc. Could you mention which tools and > versions > that must to be used in order to build LLVM on ARM Linux EABI > platform. > > Thanks, > > Mikaël. > > http://www.nabble.com/file/p20...

...t;> # of unexpected failures 57 >> # of expected failures 6 >> >> The extra success test is funccall.ll from test/DebugInfo. In order >> to build >> successfully LLVM on ARM Linux EABI platform, I put in comment the >> usage of >> __register_frame into JIT.cpp because it seems that __register_frame >> function is not into my libgcc. Could you mention which tools and >> versions >> that must to be used in order to build LLVM on ARM Linux EABI >> platform. >> >> Thanks, >> >> Mikaël. >>...

...f expected passes 2727 > # of unexpected failures 57 > # of expected failures 6 > > The extra success test is funccall.ll from test/DebugInfo. In order > to build > successfully LLVM on ARM Linux EABI platform, I put in comment the > usage of > __register_frame into JIT.cpp because it seems that __register_frame > function is not into my libgcc. Could you mention which tools and > versions > that must to be used in order to build LLVM on ARM Linux EABI > platform. > > Thanks, > > Mikaël. > > http://www.nabble.com/file/p20...

...e following error while compiling llvm and clang under cygwin. >> >> /cygdrive/c/Users/brianherman/**Desktop/llvm/llvm-3.3.src/** >> Release+Asserts/lib/**libLLVMMCJIT.a(**SectionMemoryManager.o):** >> SectionMemoryManager.cpp:(.**text+0x3b): >> undefined reference to `__register_frame' >> > > I register_frame is used to enable the debugger (gdb) to debug JIT'd code. > It > is a function provided by libgcc, to be more precise in libgcc_eh. Is it > in > your copy? > > $ nm libgcc_eh.a | grep register_fram > 0000000000001960 T __deregister...

...cted failures 57 >>> # of expected failures 6 >>> >>> The extra success test is funccall.ll from test/DebugInfo. In order >>> to build >>> successfully LLVM on ARM Linux EABI platform, I put in comment the >>> usage of >>> __register_frame into JIT.cpp because it seems that __register_frame >>> function is not into my libgcc. Could you mention which tools and >>> versions >>> that must to be used in order to build LLVM on ARM Linux EABI >>> platform. >>> >>> Thanks, >>> &...

...>> # of expected failures 6 >>>> >>>> The extra success test is funccall.ll from test/DebugInfo. In order >>>> to build >>>> successfully LLVM on ARM Linux EABI platform, I put in comment the >>>> usage of >>>> __register_frame into JIT.cpp because it seems that __register_frame >>>> function is not into my libgcc. Could you mention which tools and >>>> versions >>>> that must to be used in order to build LLVM on ARM Linux EABI >>>> platform. >>>> >>>&gt...

Hi, > / : undefined reference to `__register_frame' / this is defined in libgcc on most platforms and is used for registering exception handling frames. LLVM's JIT makes use of it on some platforms. What version of gcc are you using? Ciao, Duncan.

Thanks, sands My gcc version is 3.4.6. Any problems? Shengmei ---------------- Hi, > / : undefined reference to `__register_frame' / this is defined in libgcc on most platforms and is used for registering exception handling frames. LLVM's JIT makes use of it on some platforms. What version of gcc are you using? Ciao, Duncan.

...object after several iterations over the valid FDE objects. So it looks like an invalid FDE object is attached to the valid ones. Also when I split two JIT runs into the separate processes nothing crashes. As I understand, __deregister_frame has to be called during code removal. I can only see __register_frame call, and not __deregister_frame. Why? Yuri

Hi Christian, Thanks for sharing this. Yaron Keren has been investigating some problems in the EH frame registration code recently, and I think this may be related. It at least sounds similar to the type of variations in behavior based on code size that Yaron was seeing. -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of