public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/18654] New: mcheck should warn if threads exist Date: Fri, 10 Jul 2015 12:04:00 -0000 [thread overview] Message-ID: <bug-18654-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18654 Bug ID: 18654 Summary: mcheck should warn if threads exist Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- -lmcheck (MALLOC_CHECK_) + -pthread should warn the user. In reality -pthread always gets indirectly linked so -lmcheck should just check if a new (second) thread has ever been created in this process. Maybe it is enough if mabort() does this check - that the crash is due to unsupported mcheck usage and not due to the program's bug. One does not immediately realize all the possible reasons of a crash. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-07-10 12:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-10 12:04 jan.kratochvil at redhat dot com [this message] 2015-08-22 21:34 ` [Bug malloc/18654] " jsm28 at gcc dot gnu.org 2021-07-14 2:54 ` siddhesh at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-18654-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).