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
|
2
|
3
(3) |
4
|
5
(7) |
|
6
|
7
|
8
(6) |
9
|
10
|
11
|
12
|
|
13
(1) |
14
|
15
(1) |
16
|
17
(2) |
18
|
19
(1) |
|
20
(2) |
21
(2) |
22
(2) |
23
|
24
|
25
|
26
|
|
27
|
28
(2) |
29
|
30
(1) |
31
|
|
|
|
From: John R. <jr...@bi...> - 2019-10-05 03:43:44
|
> I just pulled and built Valgrind master branch,
On which hardware architecture and operating system?
> and used it to sanitize a simple C test program (test program is "int main() { return 0; }". In order to learn more about the Valgrind internals, I thought to step through bits of it using GDB.
>
> However when I run my program under GDB I get the following segfault:
>
> $ gdb --args $HOME/p/valgrind-build/coregrind/valgrind ~/test
> ...
> (gdb) r
> ...
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000010033a8103 in ?? ()
> (gdb) bt
> #0 0x00000010033a8103 in ?? ()
> #1 0x0000001003182f40 in ?? ()
> #2 0x0000000000000000 in ?? ()
>
> I configured with CFLAGS="-g -Og"
With which compiler?
> so I'm confused as to why I'm not getting any symbols in the backtrace.
The *runtime* auto-configuration code (detect which CPU variant
and its hardware properties) might generate several signals including SIGSEGV.
Figure out why gdb is not showing symbols in the backtrace,
then get beyond the runtime configuration before complaining.
|
|
From: Jefferson C. <jef...@gm...> - 2019-10-05 02:58:41
|
Hi,
I just pulled and built Valgrind master branch, and used it to sanitize
a simple C test program (test program is "int main() { return 0; }". In
order to learn more about the Valgrind internals, I thought to step
through bits of it using GDB.
However when I run my program under GDB I get the following segfault:
$ gdb --args $HOME/p/valgrind-build/coregrind/valgrind ~/test
...
(gdb) r
...
Program received signal SIGSEGV, Segmentation fault.
0x00000010033a8103 in ?? ()
(gdb) bt
#0 0x00000010033a8103 in ?? ()
#1 0x0000001003182f40 in ?? ()
#2 0x0000000000000000 in ?? ()
I configured with CFLAGS="-g -Og" so I'm confused as to why I'm not
getting any symbols in the backtrace.
Currently investigating this problem, just wondering if it's expected
behavior for Valgrind and if there's another way to step through it with
a debugger. (That said any segfault is almost certainly a bug, so let
me know if you want me to work toward a patch)
Jefferson
|
|
From: Assad H. <ass...@li...> - 2019-10-03 17:22:48
|
On Thu, 3 Oct 2019 at 17:18, Tom Hughes <to...@co...> wrote: > > On 03/10/2019 08:25, Assad Hashmi wrote: > > > I'd like to contribute code to support ARM64, initially v8.1 instructions. > > I am a Valgrind dev newbie and wanted to check a couple of things > > before getting started. > > > > 1) I've read git-HOWTO.txt but there's no mention of reviewing patches > > before pushing. Have I missed something? > > 2) Can someone grant me write access to the Valgrind repository on the > > sourceware server? > > You should start by opening bugs and attaching your patches to > them, where they will be reviewed and committed by somebody with > commit access. > > Tom > > -- > Tom Hughes (to...@co...) > http://compton.nu/ Thanks. 369509 describes exactly what I want to do. |
|
From: Tom H. <to...@co...> - 2019-10-03 16:18:33
|
On 03/10/2019 08:25, Assad Hashmi wrote: > I'd like to contribute code to support ARM64, initially v8.1 instructions. > I am a Valgrind dev newbie and wanted to check a couple of things > before getting started. > > 1) I've read git-HOWTO.txt but there's no mention of reviewing patches > before pushing. Have I missed something? > 2) Can someone grant me write access to the Valgrind repository on the > sourceware server? You should start by opening bugs and attaching your patches to them, where they will be reviewed and committed by somebody with commit access. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Assad H. <ass...@li...> - 2019-10-03 15:53:38
|
Hello, I'd like to contribute code to support ARM64, initially v8.1 instructions. I am a Valgrind dev newbie and wanted to check a couple of things before getting started. 1) I've read git-HOWTO.txt but there's no mention of reviewing patches before pushing. Have I missed something? 2) Can someone grant me write access to the Valgrind repository on the sourceware server? Thanks |