Thanks for trying to grab a backtrace for this issue; however the trace you provided is not the same as in the original bug report - its actually a trace for normal operation of samba (which uses SIGUSR1 for signaling between processes).
I think we can see that a null pointer being passed is causing the issue - but we still need to figure out why this happens.
Please could reporters of this issue set the log level to 5:
log level 5
in /etc/samba/smb.conf, reload smbd and try to reproduce again - hopefully samba will provide some useful debug messages which might help ID whats going on.
Hi Taylor
Thanks for trying to grab a backtrace for this issue; however the trace you provided is not the same as in the original bug report - its actually a trace for normal operation of samba (which uses SIGUSR1 for signaling between processes).
Again the original trace looks similar to http:// lists.samba. org/archive/ samba-technical /2012-May/ 083909. html.
I think we can see that a null pointer being passed is causing the issue - but we still need to figure out why this happens.
Please could reporters of this issue set the log level to 5:
log level 5
in /etc/samba/ smb.conf, reload smbd and try to reproduce again - hopefully samba will provide some useful debug messages which might help ID whats going on.