search for: open_stackdumpfil

...e: line 51: 1968 Segmentation fault (core dumped) ( PATH="/nonexistent;."; conf$$.sh ) >/dev/null 2>&1<br> ./configure: line 58: 5272 Segmentation fault (core dumped) ( ( MAIL=60; unset MAIL ) || exit ) >/dev/null 2>&1<br> 0 [main] sh 4000 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump<br> 0 [main] sh 6116 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump<br> 0 [main] sh 3592 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump<br> 0 [main] sh 816 open_stackdumpfile: Dumping stack trace...

Graham, good morning. To build LLVMHello on cygming, you should configure llvm with --enable-shared . Even with enable-shared, you might build lib/Transforms/Hello manually. (yeah, on cygming, LLVMHello should depend on tools/llvm-shlib) And, you'd be better to build with --enable-optimized. With enable-shared, llvm-shlib tends to fail with too many debug symbols. HTH, ...Takumi

...and use Cygwin's GCC 4.5.3) If I instead use --enable-optimized, everything builds, however any invocation of clang.exe now halts with a segmentation fault, as shown: clang hello.c fails: 0 [main] clang 3608 exception::handle: Exception: STATUS_ACCESS_VIOLATION 10619 [main] clang 3608 open_stackdumpfile: Dumping stack trace to clang.exe.stackdump clang: error: unable to execute command: Segmentation fault (core dumped) clang: error: clang frontend command failed due to signal 2 (use -v to see invocation) clang: note: diagnostic msg: Please submit a bug report to http://llvm.org/bugs/ and include...

I've built LLVM/Clang from svn under Cygwin on Windows 7. I'd like to build on the LLVMHello pass example, however, when I try: $ cd $LLVM/lib/Transforms/Hello $ make I receive a large number of errors which start with: llvm[0]: Linking Debug+Asserts Loadable Module LLVMHello.dll /cygdrive/c/Users/Graham/home/projects/llvm_cygwin/lib/Transforms/Hello/Debug+Asserts/Hello.o: In function

...ot;/cygdrive/c/openssl.exe enc -des3 -pass pass:whatever -a" /cygdrive/c/backup user@dir: to crypt files to be sent at source with openssl. At some point rsync fails an i get 104435520 [main] rsync 1040 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 104436464 [main] rsync 1040 open_stackdumpfile: Dumping stack trace to rsync.exe.stackdump 107286788 [main] rsync 1040 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 107318448 [main] rsync 1040 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack). I know this patch was updated for rsync 2.6.9 becaus...

...t; fixme:advapi:ImpersonateLoggedOnUser (0x98) > fixme:advapi:ImpersonateLoggedOnUser (0x98) > fixme:advapi:ImpersonateLoggedOnUser (0x98) > 572273 [unknown (0x32)] HandBrakeCLI 41 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION > 572687 [unknown (0x32)] HandBrakeCLI 41 open_stackdumpfile: Dumping stack trace to HandBrakeCLI.exe.stackdump > fixme:advapi:ImpersonateLoggedOnUser (0x98) > fixme:advapi:ImpersonateLoggedOnUser (0x98) > 659813 [unknown (0x34)] HandBrakeCLI 41 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION > wine: Unhandled page fault on read...

I don't know if this is the propper place to ask for new funcionality, but after searching the website i didn't find another place to do it. I'm very sorry if I`m asking this in the wrong place. It would be greatful to have crypting funcionality added to rsync, appart from using ssh to crypt transmissions. I know this is not the original purpose for rsync, but anyway it's a fact