Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Jacob Kolding
Package: libc6 Version: 2.3.2-7 Severity: normal when using the readdir function from to get dirents the dtype member of dirent is always returned as unknown. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i6

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Philip Blundell
On Sun, 2003-09-14 at 11:33, Jacob Kolding wrote: > when using the readdir function from to get dirents the > dtype member of dirent is always returned as unknown. Please supply a test program to demonstrate the problem. We also need some more information: what filesystem are you using, and whic

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Jacob Kolding
On Sun, 2003-09-14 at 13:38, Philip Blundell wrote: > On Sun, 2003-09-14 at 11:33, Jacob Kolding wrote: > > when using the readdir function from to get dirents the > > dtype member of dirent is always returned as unknown. > > Please supply a test program to demonstrate the problem. We also need

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Philip Blundell
On Sun, 2003-09-14 at 13:17, Jacob Kolding wrote: > I'm running ext2 on linux 2.2.20 but a friend of mine is running > reiserfs on 2.4.22 and have the same problem. I'm not able to reproduce this problem on i386 with kernel 2.4.22 and libc6 2.3.2-7, on an ext3 filesystem. Once I fixed the compila

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Jacob Kolding
On Sun, 2003-09-14 at 14:32, Philip Blundell wrote: > On Sun, 2003-09-14 at 13:17, Jacob Kolding wrote: > > I'm running ext2 on linux 2.2.20 but a friend of mine is running > > reiserfs on 2.4.22 and have the same problem. > > I'm not able to reproduce this problem on i386 with kernel 2.4.22 and >

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Philip Blundell
I think this is the cause of the problem: getdents64(3, 0x80497e0, 4096) = -1 ENOSYS (Function not implemented) getdents(3, /* 40 entries */, 3933) = 888 >From what I recall, the old-style getdents syscall doesn't return d_type information. You need to upgrade your kernel to one tha

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Jacob Kolding
On Sun, 2003-09-14 at 16:20, Philip Blundell wrote: > I think this is the cause of the problem: > > getdents64(3, 0x80497e0, 4096) = -1 ENOSYS (Function not > implemented) > getdents(3, /* 40 entries */, 3933) = 888 > > >From what I recall, the old-style getdents syscall doesn't retu

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Philip Blundell
On Sun, 2003-09-14 at 16:02, Jacob Kolding wrote: > But a friend of mine has the same problem with kernel 2.4.22 and > reiserfs so how can it be a kernel problem. unless it's at kernel config > option? > > attached is the strace from my friend. In this case, getdents64() is indeed being used corre

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Jacob Kolding
On Sun, 2003-09-14 at 17:08, Philip Blundell wrote: > On Sun, 2003-09-14 at 16:02, Jacob Kolding wrote: > > But a friend of mine has the same problem with kernel 2.4.22 and > > reiserfs so how can it be a kernel problem. unless it's at kernel config > > option? > > > > attached is the strace from m

Re: Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Marco d'Itri
[EMAIL PROTECTED] wrote: >I'm running ext2 on linux 2.2.20 but a friend of mine is running >reiserfs on 2.4.22 and have the same problem. I think that d_type is only available on modern 2.4 kernels when using ext2 or ext3. -- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su

Bug#210861: libc6: readdir always returns dtype as unknown

2003-09-14 Thread Daniel Jacobowitz
On Sun, Sep 14, 2003 at 05:20:59PM +0200, Jacob Kolding wrote: > On Sun, 2003-09-14 at 17:08, Philip Blundell wrote: > > On Sun, 2003-09-14 at 16:02, Jacob Kolding wrote: > > > But a friend of mine has the same problem with kernel 2.4.22 and > > > reiserfs so how can it be a kernel problem. unless

Bug#210861: marked as done (libc6: readdir always returns dtype as unknown)

2003-09-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Sep 2003 16:36:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#210861: libc6: readdir always returns dtype as unknown has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#205234: ssh is blocked

2003-09-14 Thread David Liontooth
After upgrading libc6 from the NIS-patched 2.3.2-2.agx0 at http://honk.physik.uni-konstanz.de/linux-mips/glibc/debs/ to the current sid 2.3.2-7, I can no longer ssh into the machine. The attempt produces this result: debug1: Remote protocol version 2.0, remote software version OpenSSH_3.6.1p2 De

Bug#210964: /bin/sh segfault with future libc

2003-09-14 Thread Ralph Giles
Package: libc6 Version: 2.3.2-7 I stumbled onto bug 198154 today upgrading libc on a split testing/unstable system. We happen to have 2.3.1-17 installed, and the upgrade died on the post-rm segfault. We were about to skip the script as a work-around on the assumption it was fixed, which another

Bug#205099: Unreproducible

2003-09-14 Thread Matt Zimmerman
FYI, this test program works fine for me on every unstable system I tried, both as a standalone program and a CGI via apache. Gottfried: does this happen only when you run the program by hand, or only when you run it as a CGI? If a CGI, which web server package and version are you using? -- -

Bug#202756: [jk@blackdown.de: Re: Bug#202756: nfs-kernel-server: 1.0.5-1 works with libc6 from unstable but fails with libc6 2.3.2-1 from experimental]

2003-09-14 Thread Chip Salzenberg
I'm not sure this information made it to the NFS list, so here it is. Key points: * 1.0.6 does _not_ fix the crash. * preloading libpthread.so.0 is still an effective workaround (well, more of a diagnostic, really - we can't do it for production) Juergen's conclusion seems disturbingly true

Bug#210981: libc6: printf crashes on a certain long double

2003-09-14 Thread Daniel Jacobowitz
Package: libc6 Version: 2.3.2-7 Severity: normal Try it: int data[] = {0x, 0x, 0x0cd0}; struct ieee { unsigned int mantissa1:32; unsigned int mantissa0:30; unsigned int quiet_nan:1; unsigned int one:1; unsigned int exponent:15; u