Summary: | MALLOC_CHECK_ set to 3 by startkde | ||
---|---|---|---|
Product: | [Unmaintained] kdm | Reporter: | Nico Kruber <nico.kruber> |
Component: | general | Assignee: | kdm bugs tracker <kdm-bugs-null> |
Status: | VERIFIED UPSTREAM | ||
Severity: | normal | CC: | finex, kevin.kofler, lamarque, rdieter, reavertm, wstephenson |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nico Kruber
2010-08-11 18:01:15 UTC
Fixed If it's fixed, then please, leave it RESOLVED / FIXED ;). SVN commit 1170655 by dfaure: Let's try and remember to remove MALLOCK_CHECK_ on the next 4.x.0 release, up to now we forgot every time... CCBUG: 247398 M +1 -0 RELEASE-CHECKLIST WebSVN link: http://websvn.kde.org/?view=rev&revision=1170655 again, on 4.6 MALLOC_CHECK_ is set to 3 by startkde http://websvn.kde.org/branches/KDE/4.6/kdebase/workspace/startkde.cmake?view=markup looks as if this has been forgotten once again :( Fixed again in 4.6 branch, revision 1217284 How about just keeping this disabled always, even in trunk? Developers who really want to debug memory issues can easily set MALLOC_CHECK_ on their own. What about using "kde4-config --kde-version" to know if it is a development version? [lamarque@evolucao ~]$ kde4-config --kde-version 4.6.00 (4.6.0) If release number is above 50 it is a development version, right? We can something like: kde4-config --kde-version | perl -ne 'if (/(\d+)\.(\d+)\.(\d+)/) { if ($1 > 50) { print "development\n"; } else { print "production\n"}; exit 0; }' |