On Tue, Mar 13, 2007 at 06:11:08PM -0400, Mostro Mostro wrote:
> I am witnessing the same thing. Are you seeing core dumps in
> /var/log/messages?
> 
> ####################

...

>   #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021661d]
>   #1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021674d]
>   #2 /usr/sbin/smbd [0x8020250a]
>   #3 [0xb7f9a420]
>   #4 /lib/libc.so.6(abort+0x101) [0xb7af8801]
>   #5 /usr/sbin/smbd [0x8021c9f6]
>   #6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021cbca]
>   #7 /usr/sbin/smbd(lookup_sids+0x3aa) [0x801d3bca]
>   #8 /usr/sbin/smbd [0x80106dc1]
>   #9 /usr/sbin/smbd(_lsa_lookup_sids2+0x12d) [0x8010741d]

Just to re-assure you: I would *REALLY* like to fix this
segfault, but I just have not been able to reproduce this
and nobody has been able to send me a valgrind log with
debugging symbols turned on.

So if anybody around here sees this segfault and would be
willing to let me ssh as root into the machine, please
contact me. I would certainly be able to provide you with
ssh keys, a phone number to verify the fingerprint etc.

Volker

Attachment: pgppoa2NZ0G4W.pgp
Description: PGP signature

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to