y, June 17, 2024 1:18 PM
To: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] question regarding mismatching free/delete
On 17-06-24 08:45, Thomas Wollenzin wrote:
> Hi,
>
> I have a questing regarding Valgrind report 'Mismatched free() / delete
> / delete []'
On 17-06-24 08:45, Thomas Wollenzin wrote:
Hi,
I have a questing regarding Valgrind report 'Mismatched free() / delete
/ delete []'.
I understand that Valgrind is redirecting calls to new/delete and so on
to its own. On the allocation side I see:
operator new(unsigned long) (vg_repl
eward
Sent: Monday, June 17, 2024 11:53 AM
To: Thomas Wollenzin ; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] question regarding mismatching free/delete
On 17/06/2024 10:45, Thomas Wollenzin wrote:
> Could it be that Valgrind can get confused and not resolve the ov
On 17/06/2024 10:45, Thomas Wollenzin wrote:
Could it be that Valgrind can get confused and not resolve the overloaded
operators correctly?
This can happen as a result of "differential inlining". What I mean is, you
have `new` calls `malloc` and `delete` calls `free`, and the definitions of
Hi,
I have a questing regarding Valgrind report 'Mismatched free() / delete /
delete []'.
I understand that Valgrind is redirecting calls to new/delete and so on to its
own. On the allocation side I see:
operator new(unsigned long) (vg_replace_malloc.c:487)
on the deallocation side
free (vg_
