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
(4) |
2
(1) |
3
|
|
4
|
5
(6) |
6
|
7
(7) |
8
(2) |
9
(1) |
10
(2) |
|
11
(4) |
12
(1) |
13
(4) |
14
(5) |
15
(2) |
16
(5) |
17
(2) |
|
18
(3) |
19
(12) |
20
(10) |
21
(3) |
22
(7) |
23
(4) |
24
(5) |
|
25
(3) |
26
(2) |
27
(1) |
28
|
29
(1) |
30
(1) |
|
|
From: Marcin J. <mju...@re...> - 2016-09-16 21:37:12
|
Hi everyone! At start I would like to tell that I may not know how exactly Valgrind works and how to use it for personal projects. But (as distribution developer/packager) I built lot of software. During last few years most of my work was related to AArch64 architecture and I pushed wherever I could to get Valgrind working and used there. About week ago some of my bugs against Valgrind got closed and when I read all bugs I reported in past (especially bug 359503 [1]) I decided to check how LTP (Linux Test Project) would work when run with Valgrind on AArch64 box. 1. https://bugs.kde.org/show_bug.cgi?id=359503 So I started it. Then stopped as I had some work to do and needed that box. Then started again. etc Result so far is 19 bugs reported to get system calls implemented. Hope that there will be more as I want AArch64 to be fully covered ;D But how to run LTP under Valgrind? Does it involve magic? Is it easy? 1. fetch LTP code from git://github.com/linux-test-project/ltp 2. build it 3. run "runltp -M3" I edited 'runalltests.sh' script, and changed calls to 'runltp' to have '-M3' argument added. When you go to [2] you will see logs from my runs. They are from Fedora/rawhide system. Today's one (2016_09_16-22h_25m_48s) has 'runtest/syscalls' in reverse order to catch all missing system calls earlier. 2. https://fedora.juszkiewicz.com.pl/ltp/ If you look to logs you will see that impossible things happened. For example: ----------------------------------------------------------------------------- <<<test_start>>> tag=rt_sigprocmask02_valgrind_thread_concurrency_check stime=1473974621 cmdline=" valgrind -q --tool=helgrind --trace-children=yes rt_sigprocmask02" contacts="" analysis=exit <<<test_output>>> --25286-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --25286-- si_code=1; Faulting address: 0xFFFFFFFFFFFFFF; sp: 0x802fafbe0 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==25286== at 0x3803B0CC: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0x3809B5EB: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0x3807A5CB: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0x38076F8F: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0x38078A3B: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0x380897EB: ??? (in /usr/lib64/valgrind/helgrind-arm64-linux) ==25286== by 0xFFFFFFFFFFFFFFFF: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 25286) ==25286== at 0x49CECD4: syscall (in /usr/lib64/libc-2.24.90.so) ==25286== by 0x402A9F: main (rt_sigprocmask02.c:107) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. <<<execution_status>>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=30 cstime=1 <<<test_end>>> ----------------------------------------------------------------------------- Or others. Some of those may require code changes but catching which ones is a bit beyond my knowledge. If you tell me which types should be reported as bugs I would do that next week. I would like to thank Mark Wielaard (mjw) for his help with handling most of my Valgrind issues. |
|
From: Rhys K. <rhy...@gm...> - 2016-09-16 18:42:20
|
On Friday, September 16, 2016, Julian Seward <js...@ac...> wrote: > > Hi All, > > I plan to branch for 3.12 next Monday. This is so as to make life > easier for packagers and to provide a place to work out any > stability/correctness issues before the release. The 3.12.0 release > will be on Thursday 20 October, with a possible followup 3.12.1 > release in mid December. > > I believe the trunk is in fairly good shape on Linux and Solaris. > There are still quite a few bugs though that would be good to fix > before the release, if possible. docs/internals/3_11_BUGSTATUS.txt > summarises and tracks their status. I will track checkins to the > trunk and merge to the branch as necessary. Please do let me know of > any bugs you think should be fixed for 3.12, and of any checkins to > merge. > > I am currently unsure about the status of the following ports: > > * MacOS X 10.12 A patch set that provides the initial bring up on macOS 10.12 is on Bugzilla: https://bugs.kde.org/show_bug.cgi?id=365327 I hope to address the memory mapping problem over the weekend. > > * The linux-tilegx port. Is anyone maintaining this now? > > J > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... <javascript:;> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Ivo R. <iv...@iv...> - 2016-09-16 16:09:48
|
2016-09-16 17:32 GMT+02:00 Julian Seward <js...@ac...>: > Please do let me know of any bugs you think should be fixed for 3.12, and of any checkins to merge. > Hi Julian, Patch for the following bug is ready to land, IMO. I'd like to have another set of eyeballs review the changes before I integrate it, though: 367995 Integration of memcheck with custom memory allocator Thanks, I. |
|
From: Julian S. <js...@ac...> - 2016-09-16 15:33:06
|
Hi All, I plan to branch for 3.12 next Monday. This is so as to make life easier for packagers and to provide a place to work out any stability/correctness issues before the release. The 3.12.0 release will be on Thursday 20 October, with a possible followup 3.12.1 release in mid December. I believe the trunk is in fairly good shape on Linux and Solaris. There are still quite a few bugs though that would be good to fix before the release, if possible. docs/internals/3_11_BUGSTATUS.txt summarises and tracks their status. I will track checkins to the trunk and merge to the branch as necessary. Please do let me know of any bugs you think should be fixed for 3.12, and of any checkins to merge. I am currently unsure about the status of the following ports: * MacOS X 10.12 * The linux-tilegx port. Is anyone maintaining this now? J |
|
From: <sv...@va...> - 2016-09-16 13:38:10
|
Author: sewardj
Date: Fri Sep 16 14:38:02 2016
New Revision: 15959
Log:
Update bug lists.
Modified:
trunk/NEWS
trunk/docs/internals/3_11_BUGSTATUS.txt
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Fri Sep 16 14:38:02 2016
@@ -76,6 +76,7 @@
353138 www: update "The Valgrind Developers" page
353370 don't advertise RDRAND in cpuid for Core-i7-4910-like avx2 machine
== 365325
+ == 357873
353384 amd64->IR: 0x66 0xF 0x3A 0x62 0xD1 0x62 (pcmpXstrX $0x62)
353398 WARNING: unhandled amd64-solaris syscall: 207
353660 XML in auxwhat tag not escaping reserved symbols properly
Modified: trunk/docs/internals/3_11_BUGSTATUS.txt
==============================================================================
--- trunk/docs/internals/3_11_BUGSTATUS.txt (original)
+++ trunk/docs/internals/3_11_BUGSTATUS.txt Fri Sep 16 14:38:02 2016
@@ -5,41 +5,28 @@
=== VEX/amd64 ==========================================================
-352549 Valgrind (whether with memchek or callgrind) crashes with
- "unhandled instruction bytes"
- [Probably invalid]
-
-354931 Analyze of qt app results in incompatible processor message
- [Gentoo stupidity]
-
-356392 FPU control word not updated on FYL2X with ST(0) = 0
- [Also relevant for x86]
-
356715 vex amd64->IR: 0xC4 0xE2 0x7D 0x13 0x4 0x4A 0xC5 0xFC
vcvtph2ps (%rdx,%rcx,2),%ymm0
-357873 libstdc++ unhandled instruction: 0xF 0xC7 0xF0 0x89
- [== 353370, fixed, RDRAND ?]
-
357932 vex amd64->IR: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F
rex.WB minsd (%r8),%xmm0
rex.WB maxsd (%r8),%xmm0
+ redundant rex prefixes
360415 amd64 instructions ADCX and ADOX are not implemented in VEX
- [has patch, could possibly take it]
+ [has patch, could possibly take it, but needs cleanup/verification]
367543 bt/btc/btr/bts x86/x86_64 instructions are poorly-handled wrt flags
[Z flag behaviour is wrong]
AMD XOP-prefixed insns:
-356138 vex amd64->IR: 0x8F 0xEA 0x78 0x10 0xD2 0x6 0x6 0x0
- [== 339596, possibly -- AMD XOP extensions]
356611 vex amd64->IR: 0x8F 0xEA 0xF8 0x10 0xC9 0x3 0x1D 0x0
[== 328357, still open]
339596 vex amd64->IR: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9
[AMD XOP/FMA support]
+ == 356138
=== VEX/arm ============================================================
|