While debugging the valgrind problems of bug #8215,
I've found a lot of valgrind warnings when running this
on ubuntu 10.04 64-bit:
TDB_NO_FSYNC=1 SMBD_OPTIONS="-d10" SMBD_VALGRIND="valgrind --log-file=metze.vg-smbd --num-callers=30 --track-origins=yes" make test -j TESTS="spoolss"
(The -d10 matters as this means the ndr_print code will tell us
where the unitialized memory comes from, otherwise it's really
hard to find if valgrind just complains about writev())
Created attachment 6591 [details]
The valgrind output
Created attachment 6598 [details]
This patchset fixes the warnings. Please push to master and 3.6 if they are fine with you.
Comment on attachment 6598 [details]
looks good, I pushed that patchset to master
Karolin, please add to 3.6
Pushed to v3-6-test.
Closing out bug report.