Your message dated Fri, 26 Dec 2008 07:44:10 +0100
with message-id <[email protected]>
and subject line Re: Bug#495085: We need to know if that bug happens with stock 
Debian kernels
has caused the Debian Bug report #495085,
regarding smbfs: *** glibc detected *** free(): invalid pointer: 0x08050c0a ***
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
495085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495085
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: smbfs
Version: 3.0.24-6etch10
Severity: normal


I updated to etchandhalf and compiled an own 2.6.26.1 kernel. Since I get this 
error trying to mount a cifs drive:

ben...@go:~$ /sbin/mount.cifs //reflector.EXAMPLE.COM/files reflector -o 
user=benoit,noperm
Password:
*** glibc detected *** free(): invalid pointer: 0x08050c0a ***

Any idea about the cause?

Regards
-Benoit-

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26.1
Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1)

Versions of packages smbfs depends on:
ii  lib 2.3.6.ds1-13etch7                    GNU C Library: Shared libraries
ii  lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library
ii  lib 1.4.4-7etch6                         MIT Kerberos runtime libraries
ii  lib 2.1.30-13.3                          OpenLDAP libraries
ii  net 4.29                                 Basic TCP/IP networking system
ii  sam 3.0.24-6etch10                       Samba common files used by both th

smbfs recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Quoting Benoît Panizzon ([email protected]):
> Hi Christian
> 
> > Hi Benoît (and Merry Christmas...),
> 
> Thank you, to you too.
> 
> Unfortunately I'm in holidays until the end of january so I will not be able 
> to test again until then.
> I could reproduce the problem on multiple machines but all with self compiled 
> kernel. If you can't reproduce this with a stock kernel, then close the bug 

Doing so.

I suspect something weird in your kernel compilation environment, but
this is obviously hard to investigate....and out of our own expertise.

So, as said, if you can reproduce the problem with a stock binary
kernel package, then reopen the bug (and don't forget mentioning what
kernel package you used).



Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to