On Fri, 2009-01-23 at 17:42 +1100, Paul Wankadia wrote: > On Thu, Jan 22, 2009 at 8:39 PM, Ian Kent <[email protected]> wrote: > > > I wanted to understand your position... > > > > Oh, and I've just noticed that there's a `fatal' macro that > calls > > abort(3). It seems to be used widely, but solely for > unexpected > > Pthreads errors? > > So, now it looks like I'm contradicting myself, well > called, ;) > > The fatal() function was added much later than the times we > got > complains about autofs exiting upon errors, which lead to the > common > approach of continue if at all possible. The call is used > almost > exclusively for checking pthreads call returns that should > "never" fail. > The idea is that, rather than not bother checking them, abort > so we can > see where the fail occurred and get a backtrace from the core. > > Does dmalloc provide similar functionality in the event of memory > exhaustion?
No. Dmalloc is more like valgrind but is linked in as a library. I found Dmalloc much better in pointing to trouble spots than valgrind. Unfortunately, I have not been able to get it to work for some time now and I never got the 64 bit library to function. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
