Deactivate MALLOC_CHECK_ on x86_64
Michael Pyne
mpyne at kde.org
Mon Nov 16 23:07:54 GMT 2009
On Monday 16 November 2009 17:27:04 Michael Pyne wrote:
> On Monday 16 November 2009 05:22:09 Stephan Kulow wrote:
> > But disabling MALLOC_CHECK_ on KDE makes little sense as KDE has almost
> > no way to find out if the system is affected or not - openSUSE's glibc
> > 2.10 is not. Perhaps you can apply openSUSE's patch to your glibc?
>
> Oh wait, checking the great Google reveals a possibility of what you're
> referring to: http://sourceware.org/bugzilla/show_bug.cgi?id=10282 (glibc
> bug 10282 reported about breakage in OpenSUSE Factory?)
>
> The testcase on that bug works great, so I'll see about trying the patch.
OK, it works for me. I've closed our tracking bug.
It may still be prudent to disable MALLOC_CHECK_ for glibc 2.10 (and the
recently-released 2.11), except that it's hard to automatically tell whether
the fix has been backported by the distributor or not.
Regards,
- Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091116/fa2f2778/attachment.sig>
More information about the kde-core-devel
mailing list