You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
(1) |
2
(3) |
3
(1) |
4
(2) |
|
5
|
6
|
7
(4) |
8
|
9
(2) |
10
|
11
(2) |
|
12
|
13
(3) |
14
(7) |
15
(4) |
16
(2) |
17
|
18
|
|
19
|
20
(1) |
21
(2) |
22
|
23
|
24
|
25
|
|
26
|
27
(1) |
28
|
29
|
30
|
|
|
|
From: Schmidt, A. <adr...@si...> - 2017-11-09 10:05:33
|
Valgrind’s behavior regarding wrapping new/delete changed in version 3.12.0.
From the changelog:
* Replacement/wrapping of malloc/new related functions is now done not just
for system libraries by default, but for any globally defined malloc/new
related function (both in shared libraries and statically linked alternative
malloc implementations). The dynamic (runtime) linker is excluded, though.
To only intercept malloc/new related functions in
system libraries use --soname-synonyms=somalloc=nouserintercepts (where
"nouserintercepts" can be any non-existing library name).
This new functionality is not implemented for MacOS X.
HTH,
Adriaan
From: Michael Moser [mailto:mos...@gm...]
Sent: Donnerstag, 9. November 2017 10:27
To: Val...@li...
Subject: [Valgrind-developers] valgrind3.13.0 is not calling application defined global new/delete operators.
Hi,
I have a short program that overrides global new and delete operators. When running it in valgrind 3.13.0 then the global new/delete operators of the application are not called, in valgrind 3.10.1 the global new/delete operators are called. My questions are: why this behavior in valgrind 3.13.0 ? how can we get valgrind3.13.0 to call the global new/delete of the application, is there a configuration setting/command line switch that enables this? (environment OS Linux, Ubuntu 14.04.5 LTS, x86_64)
The program.
#include <malloc.h>
#include <new>
void* operator new (size_t size_i) throw (std::bad_alloc)
{
fprintf(stderr,"new %d (operator new (size_t size_i) throw (std::bad_alloc))\n", __LINE__);
return malloc(size_i);
}
void* operator new (size_t size_i, const std::nothrow_t& nothrow_value) throw()
{
fprintf(stderr,"new %d (operator new (size_t size_i, const std::nothrow_t& nothrow_value) throw())\n", __LINE__);
return malloc(size_i);
}
void* operator new[] (size_t size_i) throw (std::bad_alloc)
{
fprintf(stderr,"new %d (operator new[] (size_t size_i) throw (std::bad_alloc)) \n", __LINE__);
return malloc(size_i);
}
void* operator new[] (size_t size_i, const std::nothrow_t& nothrow_value) throw()
{
fprintf(stderr,"new %d (operator new[] (size_t size_i, const std::nothrow_t& nothrow_value) throw()) \n", __LINE__);
return malloc(size_i);
}
void operator delete (void* p_i) throw()
{
fprintf(stderr, "delete %d (operator delete (void* p_i) throw())\n",__LINE__);
free(p_i);
}
void operator delete (void* p_i, const std::nothrow_t& nothrow_constant) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
void operator delete[] (void* p_i) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
void operator delete[] (void* p_i, const std::nothrow_t& nothrow_constant) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
#include <stdio.h>
main()
{
fprintf(stderr, "ku !\n");
char * a = new char[123];
delete [] a;
int * b = new int();
delete b;
return 0;
}
Now compile it
gcc -g valg.cpp -lstdc++
run it without valgrind
$ ./a.out
ku !
new 19 (operator new[] (size_t size_i) throw (std::bad_alloc))
delete 43
new 6 (operator new (size_t size_i) throw (std::bad_alloc))
delete 31 (operator delete (void* p_i) throw())
With valgrind 3.13.0 global operator new is not called.
valgrind ./a.out
==24181== Memcheck, a memory error detector
==24181== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==24181== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==24181== Command: ./a.out
==24181==
ku !
==24181==
with valgrind 3.10.1
valgrind ./a.out
==32055== Memcheck, a memory error detector
==32055== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==32055== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==32055== Command: ./a.out
==32055==
ku !
new 19 (operator new[] (size_t size_i) throw (std::bad_alloc))
delete 43
new 6 (operator new (size_t size_i) throw (std::bad_alloc))
delete 31 (operator delete (void* p_i) throw())
==32055==
==32055== HEAP SUMMARY:
==32055== in use at exit: 0 bytes in 0 blocks
==32055== total heap usage: 2 allocs, 2 frees, 127 bytes allocated
==32055==
==32055== All heap blocks were freed -- no leaks are possible
==32055==
==32055== For counts of detected and suppressed errors, rerun with: -v
==32055== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
|
|
From: Michael M. <mos...@gm...> - 2017-11-09 09:27:33
|
Hi,
I have a short program that overrides global new and delete operators. When
running it in valgrind 3.13.0 then the global new/delete operators of the
application are not called, in valgrind 3.10.1 the global new/delete
operators are called. My questions are: why this behavior in valgrind
3.13.0 ? how can we get valgrind3.13.0 to call the global new/delete of
the application, is there a configuration setting/command line switch that
enables this? (environment OS Linux, Ubuntu 14.04.5 LTS, x86_64)
The program.
#include <malloc.h>
#include <new>
void* operator new (size_t size_i) throw (std::bad_alloc)
{
fprintf(stderr,"new %d (operator new (size_t size_i) throw
(std::bad_alloc))\n", __LINE__);
return malloc(size_i);
}
void* operator new (size_t size_i, const std::nothrow_t& nothrow_value)
throw()
{
fprintf(stderr,"new %d (operator new (size_t size_i, const
std::nothrow_t& nothrow_value) throw())\n", __LINE__);
return malloc(size_i);
}
void* operator new[] (size_t size_i) throw (std::bad_alloc)
{
fprintf(stderr,"new %d (operator new[] (size_t size_i) throw
(std::bad_alloc)) \n", __LINE__);
return malloc(size_i);
}
void* operator new[] (size_t size_i, const std::nothrow_t&
nothrow_value) throw()
{
fprintf(stderr,"new %d (operator new[] (size_t size_i, const
std::nothrow_t& nothrow_value) throw()) \n", __LINE__);
return malloc(size_i);
}
void operator delete (void* p_i) throw()
{
fprintf(stderr, "delete %d (operator delete (void* p_i)
throw())\n",__LINE__);
free(p_i);
}
void operator delete (void* p_i, const std::nothrow_t&
nothrow_constant) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
void operator delete[] (void* p_i) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
void operator delete[] (void* p_i, const std::nothrow_t&
nothrow_constant) throw()
{
fprintf(stderr, "delete %d\n",__LINE__);
free(p_i);
}
#include <stdio.h>
main()
{
fprintf(stderr, "ku !\n");
char * a = new char[123];
delete [] a;
int * b = new int();
delete b;
return 0;
}
Now compile it
gcc -g valg.cpp -lstdc++
run it without valgrind
$ ./a.out
ku !
new 19 (operator new[] (size_t size_i) throw (std::bad_alloc))
delete 43
new 6 (operator new (size_t size_i) throw (std::bad_alloc))
delete 31 (operator delete (void* p_i) throw())
With valgrind 3.13.0 global operator new is not called.
valgrind ./a.out
==24181== Memcheck, a memory error detector
==24181== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et
al.
==24181== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright
info
==24181== Command: ./a.out
==24181==
ku !
==24181==
with valgrind 3.10.1
valgrind ./a.out
==32055== Memcheck, a memory error detector
==32055== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==32055== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==32055== Command: ./a.out
==32055==
ku !
new 19 (operator new[] (size_t size_i) throw (std::bad_alloc))
delete 43
new 6 (operator new (size_t size_i) throw (std::bad_alloc))
delete 31 (operator delete (void* p_i) throw())
==32055==
==32055== HEAP SUMMARY:
==32055== in use at exit: 0 bytes in 0 blocks
==32055== total heap usage: 2 allocs, 2 frees, 127 bytes allocated
==32055==
==32055== All heap blocks were freed -- no leaks are possible
==32055==
==32055== For counts of detected and suppressed errors, rerun with: -v
==32055== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
|