summary says it all... nmbd compiled in this way doesnt work more than hour.
would be nice to have this one solved...
This might be a duplicate of #1631.
So let me get this straight - when compiled with optimisations on nmbd crashes,
and with optimisations off it doesn't.
Tell me why this isn't a gcc compiler bug and why I can't close this bug
immediately as "not our bug" ?
Jeremy: You might close it. But I'm not sure if this is the same problem as
Roman: Reopen if you think it's a primary Samba problem.
this is what I got from ktracing the nmbd:
hudson10 ~# kdump | tail
81726 nmbd RET write 15/0xf
81726 nmbd CALL sigprocmask(0x3,0xbfbfdf10,0)
81726 nmbd RET sigprocmask 0
81726 nmbd CALL getpid
81726 nmbd RET getpid 81726/0x13f3e
81726 nmbd CALL kill(0x13f3e,0x6)
81726 nmbd RET kill 0
81726 nmbd PSIG SIGIOT caught handler=0x8099e28 mask=0xfffefedf code=0x0
81726 nmbd CALL exit(0x1)
I hope this will help...
please retest against 3.0.11 and reopen if necessary. Also reset
the version if you reopen the bug report. Thanks.
I retested this on 3.0.11 and its still there...
if ther compiler optimizations cause the crash it is a compiler bug. Bot ours.
seems to be solved in 3.0.12 (I am runing -Os samba more than 12 hours, before
it didnt survive 30 minutes)