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
|
4
|
5
|
6
|
7
|
8
|
|
9
|
10
|
11
|
12
(1) |
13
|
14
|
15
(1) |
|
16
(1) |
17
|
18
(6) |
19
(7) |
20
(3) |
21
|
22
(4) |
|
23
(3) |
24
(3) |
25
(1) |
26
|
27
|
28
(3) |
29
|
|
30
|
31
(1) |
|
|
|
|
|
|
From: Mark W. <ma...@kl...> - 2022-10-19 23:52:56
|
Greetings. A first release candidate for 3.20.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.20.0.RC1.tar.bz2 (md5 = 981b9276536843090700c1268549186e) Please give it a try on platforms that are important for you. If no serious issues are reported, the 3.20.0 final release will happen on 22 October. |
|
From: Mark W. <ma...@so...> - 2022-10-19 23:40:59
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=b112a9b37a85bdb3d1861530285162d511f78035 commit b112a9b37a85bdb3d1861530285162d511f78035 Author: Mark Wielaard <ma...@kl...> Date: Thu Oct 20 01:40:12 2022 +0200 Set version to 3.20.0-RC1 and update NEWS Diff: --- NEWS | 17 ++++------------- configure.ac | 4 ++-- 2 files changed, 6 insertions(+), 15 deletions(-) diff --git a/NEWS b/NEWS index a5c0a2d017..c40a0fc70c 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,4 @@ -Release 3.20.0 (?? Oct 2022) +Release 3.20.0 (22 Oct 2022) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, @@ -17,17 +17,8 @@ AMD64/macOS 10.13 and nanoMIPS/Linux. * The Linux rseq syscall is now implemented as (silently) returning ENOSYS. * Add FreeBSD syscall wrappers for __specialfd and __realpathat. * Remove FreeBSD dependencies on COMPAT10, which fixes compatibility with HardenedBSD - -* ================== PLATFORM CHANGES ================= - -* arm64: - -* s390: - -* ppc64: - -* ==================== TOOL CHANGES =================== - +* The option --enable-debuginfod=<no|yes> [default: yes] has been added on Linux. +* More DWARF5 support as generated by clang14. * ==================== FIXED BUGS ==================== @@ -59,7 +50,7 @@ To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed above. -(3.20.0.RC1: ?? Oct 2022) +(3.20.0.RC1: 20 Oct 2022) Release 3.19.0 (11 Apr 2022) diff --git a/configure.ac b/configure.ac index 369daa173a..196dc4c573 100755 --- a/configure.ac +++ b/configure.ac @@ -17,8 +17,8 @@ m4_define([v_major_ver], [3]) m4_define([v_minor_ver], [20]) m4_define([v_micro_ver], [0]) -m4_define([v_suffix_ver], [GIT]) -m4_define([v_rel_date], ["?? Oct 2022"]) +m4_define([v_suffix_ver], [RC1]) +m4_define([v_rel_date], ["20 Oct 2022"]) m4_define([v_version], m4_if(v_suffix_ver, [], [v_major_ver.v_minor_ver.v_micro_ver], |
|
From: Nicholas N. <n.n...@gm...> - 2022-10-19 23:07:01
|
John: I suggest you temper your tone. Mahin is a newcomer who has asked a question in good faith, and doesn't deserve an aggressive reply. Mahin: As the error message says: "Your program has a bug and erroneously jumped to a non-codelocation. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault." I suggest addressing all the errors reported by Valgrind prior to the "Unrecognised instruction" message. I also suggest checking the return value of `fopen` calls for errors. As for profiling source code, Cachegrind and Callgrind are two tools that come with Valgrind that are good for this. You can read about them in the user manual. `perf` is also a good profiling tool, as John mentioned. Finally, there is a valgrind-users email list that is more appropriate for this kind of question. This list (valgrind-developers) is more about the development of Valgrind itself, rather than its use. Nick On Thu, 20 Oct 2022 at 00:49, John Reiser <jr...@bi...> wrote: > On 10/19/22 01:40, Mahin Pandya wrote: > > I am getting below error while running Valgrind, not sure if this is bug > in Valgrind, application is build using Wine lib. > > > > Can someone check this? > > > > --------------------- > > > > … > > > > ==2214549== Invalid write of size 8 > > > > ==2214549== at 0x46C0040: setup_raise_exception (signal_x86_64.c:2158) > > > > ==2214549== by 0x46C0653: segv_handler (signal_x86_64.c:2626) > > > > ==2214549== by 0x407641F: ??? (in /usr/lib/x86_64-linux-gnu/ > libpthread-2.31.so) > > > > ==2214549== Address 0x22fbd0 is in a rw- anonymous segment > [[snip]] > > This query is so defective that we'll just ignore it until you fix it. > > 1. Which version of valgrind? Report the output from "valgrind --version". > Where did you get it? If self-built from source then report the git commit > hash and date. If pre-built from a software distribution, then report > the name and version of the distribution, and the package name and version. > > 2. Which version of Wine lib? Also give the URL for download of the > software > and installation instructions. > > 3. Which execution environment? Report the output from "sed 10q > /proc/cpuinfo" > and the VM booting banner from early lines of "dmesg". It really does > matter > which actual or Virtual Machine. > > 4. Which underlying physical hardware (Intel or AMD)? [Perhaps the same > as #3.] > > > > > Is there option I could use Valgrind for profiling source code? Any > pointers/suggestion are welcome. > > DO NOT start a profiling project using valgrind. Instead, start with > 'perf' > which is vastly more capable, flexible, and fast. > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Mark W. <ma...@so...> - 2022-10-19 22:35:46
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=6a5a689fd901e4abcd2f0fcc64adc14ea3122ad0 commit 6a5a689fd901e4abcd2f0fcc64adc14ea3122ad0 Author: Mark Wielaard <ma...@kl...> Date: Thu Oct 20 00:34:15 2022 +0200 Add none/tests/freebsd/auxv.stderr.exp-freebsd14 to EXTRA_DIST Diff: --- none/tests/freebsd/Makefile.am | 1 + 1 file changed, 1 insertion(+) diff --git a/none/tests/freebsd/Makefile.am b/none/tests/freebsd/Makefile.am index f1f8a5628b..030af12d20 100644 --- a/none/tests/freebsd/Makefile.am +++ b/none/tests/freebsd/Makefile.am @@ -8,6 +8,7 @@ EXTRA_DIST = \ auxv.stderr.exp-32on64 \ auxv.stderr.exp-freebsd13 \ auxv.stderr.exp-freebsd131 \ + auxv.stderr.exp-freebsd14 \ cp.vgtest \ cp.stderr.exp \ osrel.vgtest \ |
|
From: John R. <jr...@bi...> - 2022-10-19 13:48:30
|
On 10/19/22 01:40, Mahin Pandya wrote: > I am getting below error while running Valgrind, not sure if this is bug in Valgrind, application is build using Wine lib. > > Can someone check this? > > --------------------- > > … > > ==2214549== Invalid write of size 8 > > ==2214549== at 0x46C0040: setup_raise_exception (signal_x86_64.c:2158) > > ==2214549== by 0x46C0653: segv_handler (signal_x86_64.c:2626) > > ==2214549== by 0x407641F: ??? (in /usr/lib/x86_64-linux-gnu/libpthread-2.31.so) > > ==2214549== Address 0x22fbd0 is in a rw- anonymous segment [[snip]] This query is so defective that we'll just ignore it until you fix it. 1. Which version of valgrind? Report the output from "valgrind --version". Where did you get it? If self-built from source then report the git commit hash and date. If pre-built from a software distribution, then report the name and version of the distribution, and the package name and version. 2. Which version of Wine lib? Also give the URL for download of the software and installation instructions. 3. Which execution environment? Report the output from "sed 10q /proc/cpuinfo" and the VM booting banner from early lines of "dmesg". It really does matter which actual or Virtual Machine. 4. Which underlying physical hardware (Intel or AMD)? [Perhaps the same as #3.] > > Is there option I could use Valgrind for profiling source code? Any pointers/suggestion are welcome. DO NOT start a profiling project using valgrind. Instead, start with 'perf' which is vastly more capable, flexible, and fast. |
|
From: Mahin P. <mah...@ac...> - 2022-10-19 08:56:18
|
Hi All,
I am getting below error while running Valgrind, not sure if this is bug in Valgrind, application is build using Wine lib.
Can someone check this?
---------------------
…
==2214549== Invalid write of size 8
==2214549== at 0x46C0040: setup_raise_exception (signal_x86_64.c:2158)
==2214549== by 0x46C0653: segv_handler (signal_x86_64.c:2626)
==2214549== by 0x407641F: ??? (in /usr/lib/x86_64-linux-gnu/libpthread-2.31.so)
==2214549== Address 0x22fbd0 is in a rw- anonymous segment
…
…
==2214549== valgrind: Unrecognised instruction at address 0x46bc3d9.
==2214549== at 0x46BC3D9: __wine_syscall_dispatcher (in /usr/local/lib/wine/x86_64-unix/ntdll.so)
==2214549== by 0x170055EEF: LdrResolveDelayLoadedAPI (loader.c:3515)
==2214549== Your program just tried to execute an instruction that Valgrind
==2214549== did not recognise. There are two possible reasons for this.
==2214549== 1. Your program has a bug and erroneously jumped to a non-code
==2214549== location. If you are running Memcheck and you just saw a
==2214549== warning about a bad jump, it's probably your program's fault.
==2214549== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2214549== i.e. it's Valgrind's fault. If you think this is the case or
==2214549== you are not sure, please let us know and we'll try to fix it.
==2214549== Either way, Valgrind will now raise a SIGILL signal which will
==2214549== probably kill your program.
0508:err:seh:segv_handler Got unexpected trap 0
…
--------------------------------
Source code :
> cat a.c
#include <stdio.h>
#include <stdlib.h>
#include <locale.h>
int main (int argc, char *argv[])
{
FILE *fin;
FILE *fout;
char wc;
fin=fopen("fin","r");
fout=fopen("out.txt","w,ccs=UTF-8");
while((wc=fgetc(fin))!=EOF){
fputc(wc,fout);
printf("%c", wc );
}
fclose(fin);
fclose(fout);
printf("\nFile has been created...%d\n", getpid());
sum(1);
return 0;
}
> cat c.c
void sum(int i)
{
return ;
}
void sum1(int i)
{
return ;
}
winegcc -g -o c.o -c c.c
winegcc -g -o a.out a.c c.o
valgrind --trace-children=yes wine64 a.out.so > temp.out 2>&1
Is there option I could use Valgrind for profiling source code? Any pointers/suggestion are welcome.
regards,
Mahin
|
|
From: Paul F. <pj...@wa...> - 2022-10-19 05:21:12
|
On 10/18/22 22:03, Nicholas Nethercote wrote: > It would be great to have a new release out. Currently you have to use a > trunk build of Valgrind with Rust code because of Dwarf 5 features that > Rust uses. > > Nick Hi I'm also ready to go. A+ Paul |