On Thu, Jan 05, 2006 at 05:52:19PM +0100, Christian Perrier wrote:
> severity 346069 important
> thanks

> (rationale: up to now we have no indication that the package is
> unusable for everyone.....)

> > Using host libthread_db library "/lib/libthread_db.so.1".
> > 0x00002aaaabe0fc15 in ?? ()
> > #0  0x00002aaaabe0fc15 in ?? ()
> > #1  0xffffffffffffffc0 in ?? ()
> > #2  0x00007fffffd83d1c in ?? ()
> > #3  0x0000000000000001 in ?? ()
> > #4  0x00002aaaabdb8415 in ?? ()
> > #5  0x0000000000000001 in ?? ()
> > #6  0x0000000000010000 in ?? ()
> > #7  0x0000000000000000 in ?? ()

> > Having downgraded to samba 3.0.20b-3, I can map and browse OK.

> Is that all what is outputted?

> Steve, others, is it expected that we get so few information even with
> samba-dbg?

Only in cases of stack corruption or gdb bugs.

Does the samba log give a more useful backtrace here?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to