mcheck(3): add a notice that the current implementation is not thread-safe
Hello Michael,
mcheck is known to be unusable for quite some time with multi-threaded applications:
https://sourceware.org/bugzilla/show_bug.cgi?id=9939
Until yesterday (including many hours of bug-hunting) this fact was not known to me, thus, I would like to suggest to add a note in the mcheck(3) manual page (and probably in the GLIBC documentation as well). I think one sentence in the NOTES section should suffice.
Thanks in advance!
Best regards
Tolga Dalman
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 5408D288.1050407-gM/[email protected]
Hello Toga,
Quoted 11 lines · Tolga Dalman
Hello Michael,
mcheck is known to be unusable for quite some time with multi-threaded applications:
https://sourceware.org/bugzilla/show_bug.cgi?id=9939Until yesterday (including many hours of bug-hunting) this fact was not known to me, thus, I would like to suggest to add a note in the mcheck(3) manual page (and probably in the GLIBC documentation as well). I think one sentence in the NOTES section should suffice.
It is sometime since your mail, but FYI, notes on the thread-non-safety of mcheck() were added to the page in the last months.
Thanks,
Michael
Signature · 7 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html