search for: jitexceptionhandling

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...

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

...nce. Should it? Note that I have since discovered that this is not a problem on Windows -- the exception drops through as expected. pz On 2011-07-21, at 5:45 PM, Garrison Venn wrote: > Sorry Peter, just saw this. > > If you are still having the problem: > > Did you set: llvm::JITExceptionHandling = true; ? > > Garrison > > On Jul 12, 2011, at 19:25, Peter Zion wrote: > >> Hi All, >> >> I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch bl...

Hi! I have a little problem using LLVM and will be happy to get a solution. I need to handle in C++ code an uncaught unwind instruction while calling JIT (now I get segfault). I mean something like nonexistent ExecutionEngine::invokeFunction instead of callFunction. Setting llvm::JITExceptionHandling to true and enclosing the JIT-call within try/catch block does not help here, because there is no C++ style exception thrown, but a simple unwind instruction. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-...

...I understand your case, running ExceptionDemo with an arg of -1 emulates your scenario. Note that the ExceptionDemo example is built by the llvm make (cmake worked last I checked) with exceptions on. By default exceptions are turned off for most llvm libs. I would think that if: 1) setting: llvm::JITExceptionHandling = true; 2) building your process with exceptions on. your program should work. Hope this helps Garrison On Jul 21, 2011, at 17:47, Peter Zion wrote: > Yes, I did -- it made no difference. Should it? > > Note that I have since discovered that this is not a problem on Windows -- the...

...t; > > > Otherwise looks good to me, though that's not saying much since I don't know > > > this part of LLVM. > > > > > > It looks like that code segment has been touched by a number of people: > > > > > > 147615 rafael if (JITExceptionHandling) { > > 49924 geoffray uintptr_t ActualSize = 0; > > 91464 jyasskin SavedBufferBegin = BufferBegin; > > 91464 jyasskin SavedBufferEnd = BufferEnd; > > 91464 jyasskin SavedCurBufferPtr = CurBufferPtr; > > 82418 rnk > >...

...move EH entirely from the old JIT? If so, I'll complain ;). As you pointed out earlier the EH bits are useful for stack frames on x86_64. In particular, to get useful stack traces from gdb with JIT'ed code those EH frames need to be there. So even if other people don't currently set JITExceptionHandling for this purpose (I do in a few projects), they probably will when they see crashes. Solomon

Sorry Peter, just saw this. If you are still having the problem: Did you set: llvm::JITExceptionHandling = true; ? Garrison On Jul 12, 2011, at 19:25, Peter Zion wrote: > Hi All, > > I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch block, I call a JITted function, which...

...happy to get a solution. >> I need >> > to handle in C++ code an uncaught unwind instruction while calling JIT >> (now I >> > get segfault). I mean something like nonexistent >> ExecutionEngine::invokeFunction >> > instead of callFunction. Setting llvm::JITExceptionHandling to true >> > and enclosing the JIT-call within try/catch block does not help here, >> because >> > there is no C++ style exception thrown, but a simple unwind >> instruction. Thanks >> > in advance. >> > >> > >> > >> > _____...

On 24 November 2012 17:36, Chris Lattner <clattner at apple.com> wrote: > As others have said, unfortunately it is premature to remove the old jit. I don't know of anyone using the EH code though... It can almost certainly be removed! Cool. I will remove the EH bits by the end of the week if no one complains. > -Chris Cheers, Rafael

...CK as a result. I produce my object file using TargetMachine::addPassesToEmitFile and then I link my resulting files with: gcc -o prog input.o -fexceptions I'm sure I'm just missing some option to generate the Dwarf tables, but I can't figure out what it is. For the JIT version I set JITExceptionHandling and JITEmitDebugInfo on TargetOptions. -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Sign: Please digitally sign your emails. Encrypt: I'm also happy to receive encrypted mail. -------------- next part -------------- A non-text attachment was sc...

...move EH entirely from the old JIT? If so, I'll complain ;). As you pointed out earlier the EH bits are useful for stack frames on x86_64. In particular, to get useful stack traces from gdb with JIT'ed code those EH frames need to be there. So even if other people don't currently set JITExceptionHandling for this purpose (I do in a few projects), they probably will when they see crashes. Solomon _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi All, I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch block, I call a JITted function, which in turn calls back into my code. Everything works fine unless an exception is thrown; I would except the outermost try/catch(...) block to catch the exception thrown in my innermost

...tirely from the old JIT? If so, I'll complain ;). > > As you pointed out earlier the EH bits are useful for stack frames on x86_64. In particular, to get useful stack traces from gdb with JIT'ed code those EH frames need to be there. So even if other people don't currently set JITExceptionHandling for this purpose (I do in a few projects), they probably will when they see crashes. > > Solomon > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailma...

...t file using TargetMachine::addPassesToEmitFile and > then I link my resulting files with: > > gcc -o prog input.o -fexceptions > > I'm sure I'm just missing some option to generate the Dwarf tables, but > I can't figure out what it is. For the JIT version I set > JITExceptionHandling and JITEmitDebugInfo on TargetOptions. > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- edA-qa mort-ora-y -- -- -- -...

...cs that changed? 4. SetCurrentDebugLocation takes a DebugLoc now 5. VISIBILITY_HIDDEN is gone 6. SMDiagnostic takes different parameters 7. APIs renamed: llvm_report_error -> report_fatal_error llvm_install_error_handler -> install_fatal_error_handler llvm::DwarfExceptionHandling -> llvm::JITExceptionHandling 8. disable calls to memory_barrier. this is not correct for SMP but at least its not crashing. I'll probably have more to add to this list once I try to port our bytecode compiler. > Leading up to that date, > please make sure that the tree is stable – no regressions, etc. If > you h...

...ignored. In any case, the big question is whether the exception table is in input.o already or not. You can disassemble it and take a look. > I'm sure I'm just missing some option to generate the Dwarf tables, but > I can't figure out what it is. For the JIT version I set > JITExceptionHandling and JITEmitDebugInfo on TargetOptions. You don't have to do anything AFAIK: by default the code generators will produce an exception table. Probably you should send in your IR and the .o file. Ciao, Duncan.

On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > Hi, I found a bug in the code that generates exception tables, I've attached > what I think is the correct fix. > > When you run out of space writing to a buffer, the buffer management code > simply stops writing at the end of the buffer. It is the responsibility of > the caller to

Hi everyone, I am writing an application that uses LLVM JIT and I would like to throw an exception from the JIT and catch it in the C++ code that invokes the JIT. This does not seem to work. I've written what is hopefully a super simple demonstration to reproduce this. I would appreciate any help with this. Thank you The demonstration is composed of: 1) thrower.cpp - a source file that

Good news, everybody! It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly. This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive