Le jeudi 01 novembre 2007 à 07:38 +1100, [EMAIL PROTECTED] a écrit : > > Le mardi 30 octobre 2007 à 17:13 +0100, =?UTF-8?Q? Andr=C3=A9?= Heynatz > > a écrit :
> >> Program received signal SIGINT, Interrupt. > >> [Switching to Thread 0xb6dd98c0 (LWP 15291)] > >> 0xb7f74410 in __kernel_vsyscall () > >> (gdb) bt > >> #0 0xb7f74410 in __kernel_vsyscall () > >> #1 0xb73f61c7 in syscall () from /lib/i686/cmov/libc.so.6 > >> #2 0xb7470823 in flistxattr () from /lib/libattr.so.1 > >> #3 0xb746fa7a in attr_copy_fd () from /lib/libattr.so.1 > >> #4 0x0807a18f in save_existing_local_file (lsaver=0x81b9ac0) at > >> gedit-local-document-saver.c:435 > >> #5 0xb74a1936 in ?? () from /usr/lib/libglib-2.0.so.0 > >> #6 0x081b9ac0 in ?? () > >> #7 0xb7e2f8ac in __pthread_mutex_unlock_usercnt () from > >> /lib/i686/cmov/libpthread.so.0 > >> #8 0xb74a11c6 in g_main_context_dispatch () from > >> /usr/lib/libglib-2.0.so.0 > >> #9 0xb74a4552 in ?? () from /usr/lib/libglib-2.0.so.0 > >> #10 0x0811cb70 in ?? () > >> #11 0xffffff9c in ?? () > >> #12 0x0833c130 in ?? () > >> #13 0x00000000 in ?? () > > > > This is an entirely different issue than that of the initial bug. It > > looks like some libattr operation is hanging on CIFS filesystems. > > > > Nathan, what do you think? I'm tempted to reassign this to the kernel. > > I tend to agree. Is this on i386-based hardware? Guess so as there's > references > to 486 and 686 in the gdb stack trace - in which case, this is a very > commonly > exercised code path - all distributions, all local filesystems would go > through this > code, so likely CIFS is involved. Andre, could you please try again with a stock Debian kernel? Otherwise, you can directly file a bug in the kernel.org bugzilla. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
