similar to: v2.5.5: logging failure triggers infinite loop and core dump

Hi everybody, I use rsync v2.5.5 almost without problems, but it dumps core from time to time. Core was generated by `rsync'. Program terminated with signal 11, Segmentation fault. There is excerpt from gdb's bt: #0 0x2810106f in __sfvwrite () from /usr/lib/libc.so.4 #1 0x280fdfe1 in fprintf () from /usr/lib/libc.so.4 #2 0x281002b6 in vfprintf () from /usr/lib/libc.so.4 #3

-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.

-----BEGIN PGP SIGNED MESSAGE----- The FreeSWAN project uses rsync to keep our FTP repository up-to-date. The FTP server is at xs4all.nl, and we rsync to one of their FreeBSD boxes (xs1.xs4all.nl) over SSH. We have been experiencing core dumps from the remote rsync. Initially this was with the XS4ALL provided rsync in /usr/local/bin/rsync. Since I didn't have access to the source code for

(I am not on the rsync mailing list, so if you send a response to this message to the list, please be sure to CC me.) I first reported this bug go Red Hat in <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>. If you run rsync with a subshell through ssh.com's ssh and sshd and then kill the client with ctrl-C, the rsync server process running on the remote machine grows

-----BEGIN PGP SIGNED MESSAGE----- With rsync --server, sometimes when the remote side control-C's a transfer, rsync will immediately start consuming all available RAM. gdb shows that its recursing while trying to report the failed write: #0 0x420503ac in vfprintf () from /lib/i686/libc.so.6 #1 0x42072f74 in vsnprintf () from /lib/i686/libc.so.6 #2 0x08052ca4 in rprintf

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com

Hello users, I'm new to this list, so forgive me if this has been diskussed before. I'm trying to compile samba 2.2.5 on a Alpha box with Tru64UNIX v4.0f patchkit 6. configure went ok. While running (gnu)make I get a warning. I do not exactly know what this means and want to clarify what to do. The config line is: ./configure --prefix=/usr/local/opt/samba --exec-prefix=/usr/local \

https://bugzilla.samba.org/show_bug.cgi?id=4139 Summary: Generator process (running as daemon) hangs after kill SIGINT. Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Rsync 2.5.5; transfer via ssh; sparc-sun-solaris2.5 (Ultra 1); gcc 2.8.1. Every time rsync on this box causes boundary violation. I attached two strange examples. I have a few rsync's corefiles (100MB and above) and I can examine them. I will be grateful for any help. -Mirek <-------------------------------------------------------------------------> received 966761 names done

https://bugzilla.samba.org/show_bug.cgi?id=9798 Summary: rsync crash with SIGSEGV when read time out happens Product: rsync Version: 3.0.2 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: vijunag at

Dear developers, I am already playing with openssh + heimdal krb5 + gssapi on Tru64Unix 5.1a and Irix 6.5.20, but with no much success. The worst problem I experience is following: - gethostbyname on tru64unix returns short host name instead of fqdn. But even if I overcome this problem by appending the domain name to the lname variable in gss-genr.c file and get over this problem, gss-api does

Dear developers, to my previous post I have some additional info. I just erased all the krb5 data and set it up from scratch. Now the message in sshd debug changed to: debug1: Miscellaneous failure (see text) Decrypt integrity check failed debug1: Got no client credentials Failed gssapi-with-mic for komanek .... So it seems the problem is somewhere in the kerberos, not in openssh. Is here

Here's a resend of an old patch that is intended to avoid an infinite recursion (ending in a stack overflow) of the rwrite() function getting an error that calls rwrite(), ad naseum. I've only seen this happen when one of the sides dies due to a program error -- in that case, the connection is closed, and when we try to send an error to the other side and it generates an error, the error

http://bugzilla.mindrot.org/show_bug.cgi?id=429 mouring at eviladmin.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE Summary|SSH 3.4p1 problems on Tru64 |SSH 3.4p1 problems

Hello, I am testing Samba 3.0.0 on a Tru64Unix v 5.1b. I compile it with gcc et gnumake. I am able to start it and I can see a share. Until now, I have only one problem: Logs are full of messages like "Error loading module '/usr/local/samba/lib/charset/ISO8859-1.so': dlopen: Can't open needed library: /usr/local/samba/lib/charset/ISO8859-1.so" In fact, I don't find

http://bugzilla.mindrot.org/show_bug.cgi?id=429 Summary: SSH 3.4p1 problems on Tru64 V4.0D & Tru64 V4.0F Product: Portable OpenSSH Version: 3.4p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

I am trying to compile sshd 3.8p1 on Tru64 UNIX V4.0F Patch Level 7. Previously I've compiled the entire 3.6.1p2 distribution with no problems. The problem seems to occur when linking sshd. The linker is unable to find xcrypt and shadow_pw functions (openbsd-compat/*.c). The libopenbsd-compat seems to have built without errors. I configure as follows: CC=cc CFLAGS=-O LDFLAGS=-non_shared

Hello - I am making a first attempt at writing a simple C++ routine to print out R objects (this is a simple proof-of-concept as part of a larger package development). The relevant C++ routine is as follows: void Rwrite(SEXP fd, SEXP msg) { int *ofd = INTEGER(fd); const char * omsg = CHAR(asChar(msg)); printf("[%i] %s",*ofd,omsg); } And the corresponding interface in R is as

Hi everybody ; For a week I have a real trouble with samba and I couldn't solve this I need help My operation system is Tru64unix 4.0F and Tru64unix 5.1 Samba is alpha version 2001/11/02 17:45:20, 0] nmbd/nmbd.c:(65) Got SIGTERM: going down... 2001/11/02 20:03:27, 0] lib/pidfile.c:(87) ERROR: nmbd is already running. File /usr/local/samba/var/locks/nmbd.pid exists and process id 1073

https://bugzilla.samba.org/show_bug.cgi?id=8666 Summary: --debug=all9 fail Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au QAContact: rsync-qa at