Bug 12751 – request to document that mcheck is not thread safe.

Bug 12751 - request to document that mcheck is not thread safe.


Summary:	request to document that mcheck is not thread safe.

Status:	NEW

Product:	glibc
Classification:	Unclassified
Component:	manual
Version:	unspecified

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Roland McGrath

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-05-11 17:31 UTC by Peeter Joot
Modified:	2012-08-30 16:15 UTC (History)
CC List:	1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Peeter Joot 2011-05-11 17:31:41 UTC

Attempting to use -lmcheck on a threaded program, I was not able to locate the error in the source associated with an apparent mcheck() MCHECK_HEAD status result.  I found on stackoverflow:

http://stackoverflow.com/questions/314931/glibcs-lmcheck-option-and-multithreading

saying that mcheck is not actually thread safe, referencing the following bug report:

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

This bug is opened to request that the non-thread-safe nature of mcheck() be documented explicitly in the libc info page 'Heap Consistency Checking'.