I tried to setup a testing enviroment for samba, with one win2k machine as client, and a linux box as PDC. When i try to login with the user 'gb', samba receives a sig11, and dumps a core file. This bug is easely to reproduce. See attached files for more details (configuration, logs, gdb output, tdb files).
Created attachment 25 [details] a gdb 'where' and disass of the function before the sig11
Created attachment 26 [details] The logfile that samba produced when it crashed. Created with -D10
Created attachment 27 [details] The smb.conf i used when samba crashed
Created attachment 28 [details] All .tdb files, tared shortly after the crash secrets.tdb has been included, because it does not contain important information. It is just a test setup, and dummy passwords have been used.
please review this report and marked as fixed if already taken care of. Thanks.
Can you remove the "idmap backend = tdb" parameter and retry? Simo.
It reports this messages then. Which looks wrong too. However, it doesnt crash anymore. [2003/06/23 21:33:15, 1] sam/idmap_tdb.c:db_idmap_init(319) idmap uid range missing or invalid idmap will be unable to map foreign SIDs [2003/06/23 21:33:15, 1] sam/idmap_tdb.c:db_idmap_init(331) idmap gid range missing or invalid idmap will be unable to map foreign SIDs
Ok then I think the bug is closed, I'll take care of avoiding a module to be called to times. About ranges, if you're not using winbind then they may be ok, depending on your taste.
originally reported against 3.0.0beta1. CLeaning out non-production release versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
database cleanup