[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#766732: libc: Segfault in libc (from process "pool") accessing files shared via DAV across ethernet on another machine



On Sun, 2014-10-26 at 12:00 +0100, Aurelien Jarno wrote:
> control: tag -1 + moreinfo

> > dmesg on the Client machine reports:
> > [  699.677988] pool[1873]: segfault at 0 ip 00007f5d88066a3a sp
> > 00007f5d7d974cb8 error 4 in libc-2.19.so[7f5d87fe5000+19f000]

> The crash happens because a NULL pointer is passed to strlen(), which is
> definitely not allowed. It's therefore not a libc bug, but rather a bug
> in "pool". Where does this binary come from? I haven't been able to find
> it in the Debian archive (but I might have searched wrongly). 

Good question.
 Google "pool : segfault" leads to among others
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707681
which I believe is unrelated (cameras, USB) but (message #15) also
involves "pool" (pointing vaguely at dbus). Is "pool" related to thread
pools?

or https://bbs.archlinux.org/viewtopic.php?pid=1092046
which at least involves Nautilus so may be more closely related. This
points at Gnome bug https://bugzilla.gnome.org/show_bug.cgi?id=674659
which at least gives me some hints about running Nautilus under gdb. 

If I can dig up anything this way I'll update.
- Brian


Reply to: