SIGPIPE and DBus
thiago at kde.org
Sun Sep 23 08:10:11 PDT 2007
Steve Kreyer wrote:
> #4 0xb74e3c4e in writev () from /lib/tls/i686/cmov/libc.so.6
> #5 0xb790ff8e in dbus_malloc () from /usr/lib/libdbus-1.so.3
> #6 0xb790fff7 in dbus_malloc () from /usr/lib/libdbus-1.so.3
Your backtrace doesn't help us.
dbus_malloc doesn't call writev.
D-Bus doesn't use pipes for IPC, but local sockets. The semantics are very
similar. In special, trying to write to a socket whose reading end has
closed will generate SIGPIPE.
However, the D-Bus daemon doesn't close the socket unless the application
has sent an invalid message. Therefore, if you're getting a SIGPIPE *and*
the cause is D-Bus closing its socket, verify that your binding isn't
sending an invalid message.
It's more likely that the issue isn't D-Bus.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070923/cc045221/attachment.pgp
More information about the dbus