Date: Sat, 19 Apr 2008 02:03:27 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Markus Brueffer <markus@freebsd.org> Cc: freebsd-gnome@freebsd.org Subject: Re: Possible problem with gamin Message-ID: <1208585007.15734.61.camel@shumai.marcuscom.com> In-Reply-To: <200804151726.00373.markus@FreeBSD.org> References: <200804151726.00373.markus@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-meT3qfhoagc3OduqL1oI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-04-15 at 17:25 +0200, Markus Brueffer wrote: > Hi, >=20 > I'm currently hunting down a problem in KDE4 where kded4 (some sort of su= per=20 > daemon) hangs when shutting down KDE4. kded4 has a plugin for file monito= ring=20 > using the FAM API. >=20 > If I replace gamin with fam, the shutdown works fine, so I'm suspecting a= =20 > problem with gamin. >=20 > Attaching to the hanging kded4 process shows this (full backtrace with fu= rther=20 > debugging data is attached): >=20 > [Switching to Thread 0x8103100 (LWP 100101)] > 0x29976e61 in write () from /lib/libc.so.7 > (gdb) bt > #0 0x29976e61 in write () from /lib/libc.so.7 > #1 0x28fa3152 in write () from /lib/libthr.so.3 > #2 0x2977a1f1 in gamin_write_byte (fd=3D13, data=3D0xbfbfd69a "\n", len= =3D10) at=20 > gam_api.c:535 > #3 0x2977a4b9 in gamin_send_request (type=3DGAM_REQ_CANCEL, fd=3D13,=20 > filename=3D0x0, fr=3D0x8254730, userData=3D0x0, data=3D0x811d800, has_req= num=3D0) at=20 > gam_api.c:629 > #4 0x2977bc6d in FAMCancelMonitor (fc=3D0x817acb0, fr=3D0x8254730) at=20 > gam_api.c:1413 > #5 0x281aaca0 in KDirWatchPrivate::removeEntry (this=3D0x817ac50,=20 > instance=3D0x81bab60, e=3D0x8254704, sub_entry=3D0x0)=20 > at /usr/ports/x11/kdelibs4/work/kdelibs-4.0.3/kio/kio/kdirwatch.cpp:797 > #6 0x281a9976 in KDirWatchPrivate::removeEntry (this=3D0x817ac50,=20 > instance=3D0x81bab60, _path=3D@0x834beec, sub_entry=3D0x0)=20 > at /usr/ports/x11/kdelibs4/work/kdelibs-4.0.3/kio/kio/kdirwatch.cpp:771 > #7 0x281a9d56 in KDirWatchPrivate::removeEntries (this=3D0x817ac50,=20 > instance=3D0x81bab60)=20 > at /usr/ports/x11/kdelibs4/work/kdelibs-4.0.3/kio/kio/kdirwatch.cpp:873 > #8 0x281aa017 in ~KDirWatch (this=3D0x81bab60)=20 > at /usr/ports/x11/kdelibs4/work/kdelibs-4.0.3/kio/kio/kdirwatch.cpp:1520 > [...] >=20 > top(1) shows that both gam_server and kded4 are in 'sbwait' state. >=20 > This is on RELENG_7 (i386) with gamin-0.1.9_1. Switching between polling = and=20 > kqueue support doesn't make a difference. It would be good to see the backtrace from all gam_server threads to get an idea what gam_server is doing. kded4 has written data to the gam_server socket, and it is blocking until the data is drained. Joe >=20 > Any ideas? >=20 > Thanks, >=20 > Markus >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-meT3qfhoagc3OduqL1oI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkgJiy8ACgkQb2iPiv4Uz4fpJgCfaPi/gEf4xckV7wNWdz4hgAj2 +YAAn21ZBF9ewV7XTJKIMdzsrPAHzSAE =/QK8 -----END PGP SIGNATURE----- --=-meT3qfhoagc3OduqL1oI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1208585007.15734.61.camel>