search for: inkov

...though - I don't > see anything fundamentally different about my bitcode test that lli loads > from a file versus what the wiki JIT exception example generates at runtime. > Both should result in similar IR in memory driving the JIT to generate the > required unwind information from inkove instructions and the llvm.eh > intrinsics - there's no other magic going on in the JIT example (is there?) > > Anyway, I now have LLVM trunk from svn compiled with debug information, > which makes it easier to see what's going on. Assuming I get to the bottom > of it I'l...

...to do ought to work though - I don't see anything fundamentally different about my bitcode test that lli loads from a file versus what the wiki JIT exception example generates at runtime. Both should result in similar IR in memory driving the JIT to generate the required unwind information from inkove instructions and the llvm.eh intrinsics - there's no other magic going on in the JIT example (is there?) Anyway, I now have LLVM trunk from svn compiled with debug information, which makes it easier to see what's going on. Assuming I get to the bottom of it I'll post an update here....

...to do ought to work though - I don't see anything fundamentally different about my bitcode test that lli loads from a file versus what the wiki JIT exception example generates at runtime. Both should result in similar IR in memory driving the JIT to generate the required unwind information from inkove instructions and the llvm.eh intrinsics - there's no other magic going on in the JIT example (is there?) > > Anyway, I now have LLVM trunk from svn compiled with debug information, which makes it easier to see what's going on. Assuming I get to the bottom of it I'll post an upda...

...to do ought to work though - I don't see anything fundamentally different about my bitcode test that lli loads from a file versus what the wiki JIT exception example generates at runtime. Both should result in similar IR in memory driving the JIT to generate the required unwind information from inkove instructions and the llvm.eh intrinsics - there's no other magic going on in the JIT example (is there?) >> >> Anyway, I now have LLVM trunk from svn compiled with debug information, which makes it easier to see what's going on. Assuming I get to the bottom of it I'll post...

...H (working) or solaris 10 with openssh (non-working), hostB is always solaris 10, hostC is an embedded system) A -> (public key auth) -> B -> (password auth) -> C what we're doing from host A is basically: ssh -a -x -t -t -l userB hostB ssh -a -x -l userC hostC this command is inkoved from within a daemon. stdin/stdout of the command are pipes to the daemon (pipe()/fork()/exec()). now, when hostA is running commercial SSH everything works fine. but when using openssh as client no data is received from the ssh invoked on hostB. communication to hostC is not working. the ssh c...

Hi James, Note that the wiki example is a manual JIT example that works directly with the C++ APIs. As you know, no LLVM tools are used, just LLVM libraries. I say this to point out, that in the example, the exception mechanism is under the complete control of the developer moded by the LLVM libraries. In my mind a different example/different doc. would be needed to explain how a bit code

...; see anything fundamentally different about my bitcode test that lli loads >>> from a file versus what the wiki JIT exception example generates at >>> runtime. Both should result in similar IR in memory driving the JIT to >>> generate the required unwind information from inkove instructions and the >>> llvm.eh intrinsics - there's no other magic going on in the JIT example >>> (is there?) >>> >>> Anyway, I now have LLVM trunk from svn compiled with debug information, >>> which makes it easier to see what's going on. As...

2010/1/22 James Williams <junk at giantblob.com> > > > 2010/1/22 Duncan Sands <baldrick at free.fr> > >> Hi James, >> >> >> want to send us your testcase code? Then we can give it a whirl. >>> >>> >>> Test code is at http://giantblob.com/ehtest.tar.gz >>> >>> Thanks for the help. I apologize in