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
(3) |
2
(2) |
3
(5) |
4
|
|
5
(3) |
6
|
7
|
8
(1) |
9
(3) |
10
|
11
|
|
12
|
13
(2) |
14
|
15
|
16
(1) |
17
(1) |
18
|
|
19
(1) |
20
|
21
(3) |
22
|
23
(1) |
24
(1) |
25
(4) |
|
26
|
27
(1) |
28
(9) |
|
|
|
|
|
From: Alexandra P. H. <aha...@re...> - 2023-02-13 19:08:03
|
Hi, I've been coworking with Mark Wielaard on work which would allow to run valgrind from inside gdb. I've submitted our valgrind side of the project here: https://bugs.kde.org/show_bug.cgi?id=434057. My experimental branch can be found on sourcehut: https://git.sr.ht/~sasshka/valgrind. I also described this project on my personal blog: http://sasshkas.blogspot.com/search/label/gdb%0Avalgrind We'll appreciate any review or comments, any feedback is welcome. Also we'd like ideas about what we could do on the gdb side to make this nicer/smoother. Thank you, Alexandra |
|
From: Mark W. <ma...@kl...> - 2023-02-13 17:36:34
|
Hi valgrind developers, Thanks for those that could join. I didn't really take notes, so this is very brief. If I got something wrong, please feel free to correct. On Fri, 2023-02-03 at 11:52 +0100, Mark Wielaard wrote: > Paul suggested that we should have a developer video chat again to > discuss development issues. And I agree that would be a good thing to > set some goals for the next release in April. We would like to meet > on Friday February 10 at 16:00 UTC (17:00 CET, 11:00 EST). > > https://meet.jit.si/ValgrindDevMeeting > > Some issues we can discuss: > > - Pick a date for the April 3.21.0 release > Critical bugs that are must fix? We picked Friday April 14 for the RC and Friday April 28 for the final release. But we didn't designate any critical must fix bugs (yet?) > - Upstreaming risc-v - https://github.com/petrpavlu/valgrind-riscv64 Petr explained the current status, it is fairly far along, but probably won't make the next release. https://github.com/petrpavlu/valgrind-riscv64/blob/riscv64-linux/README.md Note that the gcc compile farm has riscv hardware now: https://cfarm.tetaneutral.net/machines/list/ In general valgrind developers can request access to these machines. https://cfarm.tetaneutral.net/users/new/ > - AVX512 status - https://bugs.kde.org/show_bug.cgi?id=383010 We lost contact with the Intel group that was working on this. There are still some issues with it. It needs someone with enough time to work on it. > - loongarch - https://bugs.kde.org/show_bug.cgi?id=457504 This is split in several small patches and the contributor is really responsive. We should split the patches in those that change the core code and those that are are just for the loongarch backend. The gcc compiler farm does have two (experimental) machines: https://cfarm.tetaneutral.net/news/37 > - The macOS port status - do we have any users/developers? There is an active fork: https://github.com/LouisBrunner/valgrind-macos > - https://bugs.kde.org/show_bug.cgi?id=433859 aligned and sized stuff. > Do we have enough bits to track this efficiently? This is for C23, which isn't standard yet. So it won't need to go in soon. Julian said that he often disables the alloc/free/new/delete matching because it gets confused with some c++ allocators (?). It wasn't clear if there is a good solution for that. > - Plugging into the new FORTIFY_SOURCE=3 support in glibc. valgrind > memcheck should be able to show useful information about the memory > block that triggered the fault. After the meeting Sam found a glibc bug describing the idea: https://sourceware.org/bugzilla/show_bug.cgi?id=20644 > - Infrastructure stuff. We are still using the sourcefore mailinglist > and the kde bugzilla. But our git repo and website are at > sourceware. Should we migrate everything to sourceware? It is all a little clunky not having everything in one place. But nobody seemed to look forward to having to migrate. Also do we need people's opt-in/out consent for moving subscriptions? > - Would that be a good point to switch from "master" to "main" for the > main git branch name? We already largely avoid terms like > black/whitelist and master/slave in the code and it would be a good > transition towards more inclusive language as described in > https://inclusivenaming.org/ We'll switch the default branch to main (with master being an alias) after the release. > These are all just suggestions. Please feel free to join and/or > propose other topics, features or bugs to discuss. We also briefly discussed: - https://bugs.kde.org/show_bug.cgi?id=402833 memcheck/tests/overlap testcase fails, memcpy seen as memmove The issue is if through ifuncs both memcpy and memmove point to the same address/function. It isn't clear whether there is a good solution (we probably need to recognize these functions before doing the ifunc resolving?). If not, maybe we should stop doing overlap checks for memcpy by default. - https://bugs.kde.org/show_bug.cgi?id=434057 Add stdio mode to valgrind's gdbserver This is something which Sasha and I have been working on so you can run a program under valgrind from gdb directly. Sasha will post a little overview of the current state. |