Andrew Bartlett <[EMAIL PROTECTED]> hit the keyboard. Afterwards the following was on the screen:
> On Fri, 2005-04-08 at 01:08 +0200, Rasmus Bøg Hansen wrote: >> Hi again >> >> Valgrind is not in woody, so I installed it from backports, and made >> the following trace: >> >> valgrind -v -- smbd -i > /tmp/valgrind.log 2>&1 >> >> Output is here: >> >> http://www.amagerkollegiet.dk/~moffe/valgrind.log > > Sorry, that doesn't help. We will probably need --num-callers=32, and > we need to show it crashing, not just running and exiting once (which is > what -i does). > > Internally, Samba has been modified to assist in this, so if you run > with the valgrind --trace-children option, but not smbd's -i, the > valgrind errors will end up in the normal Samba logfiles (we redirect > stderr). Ok, I now did: valgrind -v --num-callers=32 --trace-children=yes --log-file=valgrind.log -- smbd I do not really understand (perhaps due to my limited knowledge of valgrind) why smbd crashes when run normally; when run through valgrind it seems to run without crashing. Nonetheless, the valgrind logfile is here: http://www.amagerkollegiet.dk/~moffe/valgrind.log.pid2456 Regards /Rasmus -- -- [ Rasmus "Møffe" Bøg Hansen ] --------------------------------------- 42.3454% of statistics are completely made up - Matt Benneke ----------------------------------------------[ moffe at zz9 dot dk ] --
