similar to: [LLVMdev] object file/linking is missing my exception handlers

Hi, On 11/04/13 06:06, edA-qa mort-ora-y wrote: > I have some exception handling which works fine using the JIT. Now I am > producing object files and linking them, but the exception handling > tables seem to be missing. I call _Unwind_RaiseException and get > _URC_END_OF_STACK as a result. you will get this if no catch clauses match (eg because there are no catch clauses, perhaps

On Oct 17, 2013, at 7:24 PM, edA-qa mort-ora-y <eda-qa at disemia.com> wrote: > On 17/10/13 23:57, Bill Wendling wrote: >> There shouldn't be any special linker flags you need to use. If >> you're getting segfaults, it's probably trying to access the data at >> an invalid location or something. Make sure that your EH table is >> properly aligned. You

On 17/10/13 23:57, Bill Wendling wrote: > There shouldn't be any special linker flags you need to use. If > you're getting segfaults, it's probably trying to access the data at > an invalid location or something. Make sure that your EH table is > properly aligned. You might want to hand calculate the values to make > sure that they're correct. What platform are you

I'm getting an error that I don't know how to fix. I've isolated the input as much as I easily can. I've attached the file that produces the problem. Just calling "llc err.ll -o err.s" generates the error. I'm going to try and isolate even further, but as I'm not sure what I'm looking for I don't know if I'll be successful. Does anybody know what this

4.8-stable as/of jun 9th (update scheduled) has gcc version, 2.95.4 i'm building mod_php3 (some local stuff needs a php3 processor) with mysql support. using the mysql323 client/server from ports. mysql (which i know i've built before on older stable's) reports gcc can't convert longlong to something or other... basicly saying i need a newer compiler. i'm installing gcc33

I can confirm now that my personality handler is invoked (I call setHasUWTable on the functions now, but I'm not sure if that was the difference). In any case it appears the behaviour of the tables/handling is slightly different between the JIT and GCC linked. I'm trying to figure out what this is now. On 11/04/13 06:06, edA-qa mort-ora-y wrote: > I have some exception handling which

I've reduced the example down to a minimum. The error is quite perplexing since the IR appears fine. It is a nonsensical infinite loop now, but that shouldn't be a problem. declare i64 @leaf_exception_personality(i64, i32, i64, i8*, i8*) declare i8* @count_malloc(i64) define internal i8 @junk___init_module_get_args_3() #0 { entry: %_exception = alloca { i8*, i64 } %ignore0 = invoke

I am having some trouble getting my catch clauses to appear as expected in the dwarf exception tables. I have an instruction like this: %0 = landingpad i64 personality i32 (i32, i32, i64, i8*, i8*)* @leaf_exception_personality catch i8* inttoptr (i64 987 to i8*) catch i8* inttoptr (i64 2453 to i8*) In my exception handler I walk through the records. I always get the correct

I found the problem : my code sets JITEmitDebugInfo after creating the JIT. This causes the JITDwarfEmitter DE to not be constructed in the ctor of JITEmitter (JITEmitter.cpp around line 375). Not sure if it's documented anywhere that JITEmitDebugInfo must be set before constructing the JIT, but looking at the code, it makes sense. Easy enough to fix on my side. Christophe On 19 avr. 2011,

Hello, I'd like some advice on a crash that we have observed on MacOSX with the 2.8 and 2.9 releases of LLVM, but not on the top of trunk. The crash is a null-deref in llvm::JITDwarfEmitter::EmitDwarfTable : Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 0x0000000100852203 in llvm::JITDwarfEmitter::EmitDwarfTable

With the same source code, gdb on Linux shows function names and on MacOS it doesn't. Why would MacOS be different in respect of this issue? Yuri

Because OS X is not an ELF target, and support was only implemented in LLVM for making ELFs with debug info. I think the docs I wrote on this may suggest that the FSF gdb 7.0+ will work, but that's not the case. Sent from phne Reid On Jan 4, 2011 10:50 PM, "Yuri" <yuri at rawbw.com> wrote: With the same source code, gdb on Linux shows function names and on MacOS it

I'm starting my exception handling and I am getting this error while running: parse: /home/opt/llvm/include/llvm/ADT/SmallVector.h:126: reference llvm::SmallVectorTemplateCommon<llvm::EVT>::operator[](unsigned int): Assertion `begin() + idx < end()' failed. Stack dump: 0. Running pass 'X86 DAG->DAG Instruction Selection' on function '@_wrapped_entry' This is

On 06/21/2010 14:14, Reid Kleckner wrote: > Since FreeBSD is an ELF target, this should work fine. I've also > tested that this works in 32-bit by building gdb and llvm in 32-bit > mode and testing this stuff while running on a 64-bit OS. > > I would try setting a breakpoint in gdb on > 'llvm::JITDebugRegisterer::RegisterFunction' to see that it is being > called,

This may be bogus, but do you have: llvm::JITExceptionHandling = true; for the code that generates the dynamic code? It has been a while, but I don't recall what will happen when dynamic code, generated with jit exception handling turned off, invokes libraries which in turn try to unwind the stack via the libunwind api. However given that you say the code works with 2.8, my concern

Hello, We have been investigating a crash in our application that may be related to how stack frames are generated by the JIT. We observe it with LLVM 2.9, but not with LLVM 2.8, everything else being the same. The crash occurs when dynamically generated code calls code that tries to unwind the stack. Here is what the stack trace looks like on MacOSX 10.6 : 0 libSystem.B.dylib

Hi Bill, >> The unwinder delegates the decision of whether to stop in a call frame to >> that call frame's language-specific personality function. Not all personality >> functions guarantee that they will stop to perform cleanups. I was talking about who decides what to do if there are only cleanups all the way up the stack (in C++ the program is terminated without

On Sep 27, 2011, at 4:58 AM, Duncan Sands wrote: > Hi Bill, > >>>> I'm looking at the docs, and while it refers to a "catch-all" clause, >>> >>> hopefully Bill will get rid of the first reference to "catch-all" since >>> that section is inaccurate. >>> >> I *think* this is now correct. Please check. :) >

Hey Folks- I''m trying to setup a new test/spec harness for testing Merb. I was wondering if there is a way to mock the Mongrel request, response objects easily to test my handler without actually running a server? I can easily do the env hash but I''m not entirely sure what needs to go in the request StringIO object that gets passed into my mongrel handler''s

Anyone know where I can find some sample handlers? Has an API been released yet? Br, Morten