[Digikam-devel] [Bug 196994] digikam 1.0.0-0.1.beta1.f11 from kde-redhat crash on startup

[mps]

https://bugs.kde.org/show_bug.cgi?id=196994





--- Comment #15 from mps <moabi2000 gmail com>  2009-06-20 14:39:32 ---
The malloc man page says:

"Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x) include a
malloc implementation which is tunable via environment variables. When
MALLOC_CHECK_ is set, a special (less efficient) implementation is used which
is designed to be tolerant against simple errors, such as double calls of
free() with the same argument, or overruns of a single byte (off-by-one bugs).
Not all such errors can be protected against, however, and memory leaks can
result. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently
ignored and an error message is not generated; if set to 1, the error message
is printed on stderr, but the program is not aborted; if set to 2, abort() is
called immediately, but the error message is not generated; if set to 3, the
error message is printed on stderr and program is aborted. This can be useful
because otherwise a crash may happen much later, and the true cause for the
problem is then very hard to track down.".

So why for betas is MALLOC_CHECK_ set to 2 instead of 3? I would have thought
the error message would be useful?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.