Bug 853175 - debugmode: glibc mcheck does not work (with threads)
Summary: debugmode: glibc mcheck does not work (with threads)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-30 16:29 UTC by Jan Kratochvil
Modified: 2014-03-17 03:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-20 03:06:40 UTC


Attachments (Terms of Use)

Description Jan Kratochvil 2012-08-30 16:29:30 UTC
Description of problem:
According to
  http://stackoverflow.com/questions/314931/glibcs-lmcheck-option-and-multithreading
  -> http://sourceware.org/bugzilla/show_bug.cgi?id=6547
using MALLOC_CHECK_ breaks programs using threads.
This unfortunately means MALLOC_CHECK_ is not applicable globally at all, it causes false crash positives.

Version-Release number of selected component (if applicable):
debugmode-9.34.3-1.fc16.x86_64

How reproducible:
Did not try myself but just read a bugreport.

Steps to Reproduce:
http://sourceware.org/bugzilla/show_bug.cgi?id=6547

Additional info:
MALLOC_CHECK_ is not applicable, checked also glibc sources PR 6547 is still valid.
MALLOC_PERTURB_ seems to be safe and working according to glibc sources.
G_SLICE=debug-blocks is unrelated and robably still applicable.

I got notified about it in:
  http://sourceware.org/ml/gdb/2012-08/msg00097.html

Comment 1 Bill Nottingham 2012-08-30 16:44:01 UTC
Well, that's dumb. Jeff, any chance that is fixable these days?

Comment 2 Jeff Law 2012-09-18 12:55:45 UTC
Not without a redesign of the interfaces used by malloc_check.  They simply weren't ever designed with multi-threaded access in mind and are inherently broken.

I don't think this has bubbled up high enough on anyone's radar right now.

Comment 3 Bill Nottingham 2012-09-25 05:24:04 UTC
OK, fixed in git.

Comment 4 Fedora Update System 2012-10-05 18:23:36 UTC
initscripts-9.41-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/initscripts-9.41-1.fc18

Comment 5 Fedora Update System 2012-10-06 05:28:29 UTC
Package initscripts-9.41-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing initscripts-9.41-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15530/initscripts-9.41-1.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-10-08 23:54:01 UTC
Package initscripts-9.41-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing initscripts-9.41-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15530/initscripts-9.41-2.fc18
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-11-15 22:20:18 UTC
initscripts-9.37.2-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/initscripts-9.37.2-1.fc17

Comment 8 Fedora Update System 2012-11-15 22:23:24 UTC
initscripts-9.34.4-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/initscripts-9.34.4-1.fc16

Comment 9 Fedora Update System 2012-11-20 03:06:42 UTC
initscripts-9.37.2-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2012-11-24 03:30:51 UTC
initscripts-9.34.4-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.