Package: libxmlrpc++0 Version: 0.7+cvs20040713-2 Severity: normal When the remote end disconnects suddenly the XmlRpc socket layer causes a SIGPIPE to be generated to the application since it only detects some errors on failure of send(). This can be reproduced by creating a server with a long running method and then killing the client while that method is executing.
This can be avoided by using MSG_NOSIGNAL when calling send(). Applications can also handle SIGPIPE, though this makes it more difficult for them to use the signal for their own ends. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.20-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libxmlrpc++0 depends on: ii libc6 2.5-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.2-7 GCC support library ii libssl0.9.8 0.9.8e-4 SSL shared libraries ii libstdc++6 4.1.2-7 The GNU Standard C++ Library v3 libxmlrpc++0 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
