[Bug 218741] New: [PATCH] Memcheck does not detect malloc/new/new[] mismatches in applications with custom allocators

[Steve VanDeBogart]

https://bugs.kde.org/show_bug.cgi?id=218741

           Summary: [PATCH] Memcheck does not detect malloc/new/new[]
                    mismatches in applications with custom allocators
           Product: unknown
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: vandebo-valgrind at nerdbox.net


Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

The client request VG_USERREQ__MALLOCLIKE_BLOCK does not allow the caller to
specify the allocation type (malloc,new,new[]) and therefore memcheck can not
detect mismatches between the allocation and free type.

A prime example of where this is a problem is in bug 217615
(http://bugs.kde.org/show_bug.cgi?id=217615)

One likely reason that this isn't already implemented is that the MC_Chunk
structure is short on space to store addition state.

Attached is a patch that adds additional user requests to mark block as
new-like and new[]-like.  It steals a bit from ExeContext in order to store the
additional state.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.