[Bug libc/18654] New: mcheck should warn if threads exist

[Bug libc/18654] New: mcheck should warn if threads exist

[jan.kratochvil at redhat dot com]

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.

[Bug malloc/18654] mcheck should warn if threads exist

[jsm28 at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=18654

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libc                        |malloc

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug malloc/18654] mcheck should warn if threads exist

[siddhesh at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=18654

Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at sourceware dot org

--- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
mcheck and MALLOC_CHECK_ are distinct debugging features.  MALLOC_CHECK_ is
fine, it's mcheck that doesn't work well with threads.  Given the general
brokenness of mcheck, I am inclined towards gradually pulling the plug on it. 
Newer targets don't even have __malloc_initialize_hook that is needed to make
-lmcheck work.

-- 
You are receiving this mail because:
You are on the CC list for the bug.