If you have the time to track this down, it might be worth doing a git bisect. It will require compiling samba about 7 times and testing each one.
Basically you clone the samba repository (as per the Samba 4 HOWTO on the wiki) and then: 1.) $ git bisect start samba-4.0.5 samba-4.0.4 2.) Compile samba as normal and test the result. 3.) If it fails, run "git bisect bad". If it works properly, run "git bisect good". 4.) If git tells you it's found the bad commit, report that here. Otherwise it will tell you roughly how many steps are left and what commit you are on now, in which case, go back to step 2. When git bisect tells you the bad commit, you can report that here and it might help the Samba developers to find the problem more easily. To get your git tree back to where it was before starting the bisect, do "git bisect reset". On 29 April 2013 10:56, <[email protected]> wrote: > Hi all, > > just as info, i also have the same crash with debian wheezy and samba 4.0.5, > by just doing > wbinfo --uid-info 3000000 and also only when the nssswitch.conf have "compat > winbind" > > but i didn't have this crash with 4.0.4, in this case NO problem. > > best regards > philippe > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba -- Michael Wood <[email protected]> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
