Comment 12 for bug 913991

On Jan 06, 2012, at 04:49 AM, <email address hidden> wrote:

>It doesn't seem like this code should get executed since it seems to be
>disabled in the non-debug package build, but commenting it out and rebuilding
>the package on precise and I can't reproduce the aborts.
>
>It also seems like quite a few processes are leaking file descriptors. Running
>your first dbus-daemon example in the last comment under gdb will also cause
>the abort unless I manually set FD_CLOEXEC on fd 3-6 before attempting to
>launch the service. Likewise, running dbus-daemon with --fork will trigger the
>aborts.

I'm still confused. I think we've established that the child is SIGABRTing
when DBUS_FATAL_WARNINGS=1 because some warning occurs when dbus-launch execs
the child. But I'm still at a loss to know exactly *which* warning is
occurring as there is no output that I ever see, even with DBUS_VERBOSE=1.
Nothing on stdout/stderr and nothing in any log file. So perhaps the former
are getting closed before the warnings are occurring? Have you actually seen
any warnings during normal operation when reproducing this problem?

I'm also trying to understand the difference between Ubuntu and Debian here,
as I'm fairly sure Ubuntu doesn't carry any relevant dbus delta from Debian,
so perhaps there's some other environmental interaction, that's only shown up
since Ubuntu 11.04 (IIRC).