Version: (using KDE 4.2.0)
Installed from: Fedora RPMs
In startkde Malloc_check_ is set to 2, which means that any malloc errors will result in aborting the program.
This setting also applies then to any program called from konsole.
I and others spent substantial time debugging programmes that did not run for this reason and aborted without any message.
I wonder if it is not better to set it to 1, which means that an error message is produced.
The current setting seems over-cautious.
+1. That took me a lot of time too when I was trying to figure out what was causing the following crash in a gnome app (subtitleeditor)...
I am reassigning the bug to you, Dirk, since you introduced this code in startkde (according to svn blame).
SVN commit 932527 by dfaure:
Set MALLOC_CHECK_ to 1 in release/relwithdebinfo modes, and 2 only in the other modes (debug etc.)
Otherwise some gnome apps crash more often, says comment #1 in 185225 :-)
Note, however, that any app which crashes with MALLOC_CHECK_=2 is BUGGY and needs to be fixed...
(But indeed in release mode the goal is to minimize crash risks, hence this commit).
M +9 -0 ConfigureChecks.cmake
M +1 -1 startkde.cmake
WebSVN link: http://websvn.kde.org/?view=rev&revision=932527
SVN commit 932766 by dfaure:
Remove this altogether, it was intended to be only in trunk, not in stable branch nor releases, says dirk.
M +0 -8 ConfigureChecks.cmake
M +0 -4 startkde.cmake
WebSVN link: http://websvn.kde.org/?view=rev&revision=932766
*** Bug 196207 has been marked as a duplicate of this bug. ***
This needs to be fixed on trunk too. Reopening
Closing. I misread David comment about this being activated on trunk on purpose.
This check has been removed from the 4.3 release in revision 988394
r932767 | dfaure | 2009-02-27 13:43:19 +0100 (Fri, 27 Feb 2009) | 3 lines
revert r932525 (=1 leads to a debug msg from glibc on every binary being started, even "ls")
There is now code in trunk to set MALLOC_CHECK_ to 3 (abort with error message) if glibc is of a recent enough version.