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
|
4
|
5
|
6
|
|
7
|
8
(1) |
9
(3) |
10
(2) |
11
(2) |
12
(8) |
13
(5) |
|
14
(2) |
15
|
16
|
17
(4) |
18
(2) |
19
(2) |
20
(1) |
|
21
(2) |
22
(4) |
23
(6) |
24
(2) |
25
|
26
(3) |
27
(1) |
|
28
|
29
(1) |
30
(1) |
|
|
|
|
|
From: Bart V. A. <bva...@ac...> - 2021-11-23 23:11:21
|
On 11/23/21 2:42 PM, Paul Floyd wrote: > https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=49fe0dc74a07ea4c5077867e44127eb68466eded > > commit 49fe0dc74a07ea4c5077867e44127eb68466eded > Author: Paul Floyd <pj...@wa...> > Date: Tue Nov 23 23:37:02 2021 +0100 > > Anticipate testcase problems with GCC 12 > > There will be a lot more to come. > > On amd64 Linux > In faultstatus was seeing the division by zero and emitting a ud2 opcode. > In wrap3 a pair of mutually recursive functions were being inlined. > When forced not to be inlined GCC merged them into a single function. > It cannot see that the client requests have diffeent behaviour. Hi Paul, Has it been considered to change the compiler flags instead of the test case source code? Thanks, Bart. |
|
From: John R. <jr...@bi...> - 2021-11-23 23:08:41
|
On 11/23/21 08:46, Ambalu, Robert wrote: > 0x62 0xF1 0xFD 0x8 0x6F 0x44 0x24 0xA 0xC7 0x43 This is vmovdqa64 0xa0(%rsp),%xmm0 which requires CPU feature flag AVX512VL/AVX512F which is not supported by valgrind 3.18.1. In the results of the emulated CPUID instruction, valgrind tells the running application that AVX512 is not supported. It is a bug in pyarrow ( python ) that its initialization routine does not check the cpu feature flags, and switch its later run-time instructions appropriately. Please report this bug to the maintainers of pyarrow. Modern run-time libraries use the STT_GNU_IFUNC feature to choose at run time which instruction set is available and may be used. pyarrow (and/or python3 itself) must upgrade. Gcc supports compile-time feature flags to avoid generating code that uses certain instructions. Run "info gcc" and search for "avx512", paying attention to the flags beginning with "-mavx512", and in particular the "-mno-avx512" variants. Some software administration systems for installing and maintaining software packages can limit the hardware features that packages may assume. You may be able to work-around valgrind's non-support for AVX512 by telling the packaging system to avoid the package variants which require AVX512. |
|
From: Paul F. <pa...@so...> - 2021-11-23 22:42:20
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=49fe0dc74a07ea4c5077867e44127eb68466eded commit 49fe0dc74a07ea4c5077867e44127eb68466eded Author: Paul Floyd <pj...@wa...> Date: Tue Nov 23 23:37:02 2021 +0100 Anticipate testcase problems with GCC 12 There will be a lot more to come. On amd64 Linux In faultstatus was seeing the division by zero and emitting a ud2 opcode. In wrap3 a pair of mutually recursive functions were being inlined. When forced not to be inlined GCC merged them into a single function. It cannot see that the client requests have diffeent behaviour. Diff: --- memcheck/tests/wrap3.c | 6 ++++-- none/tests/faultstatus.c | 4 +++- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/memcheck/tests/wrap3.c b/memcheck/tests/wrap3.c index 1510d1311f..c6c552d5df 100644 --- a/memcheck/tests/wrap3.c +++ b/memcheck/tests/wrap3.c @@ -5,17 +5,19 @@ /* Check that function wrapping works for a mutually recursive pair. */ -static int fact1 ( int n ); -static int fact2 ( int n ); +int fact1 ( int n ); +int fact2 ( int n ); /* This is needed to stop gcc4 turning 'fact' into a loop */ __attribute__((noinline)) int mul ( int x, int y ) { return x * y; } +__attribute((noinline)) int fact1 ( int n ) { if (n == 0) return 1; else return mul(n, fact2(n-1)); } +__attribute((noinline)) int fact2 ( int n ) { if (n == 0) return 1; else return mul(n, fact1(n-1)); diff --git a/none/tests/faultstatus.c b/none/tests/faultstatus.c index 1b583d9d42..458ea82645 100644 --- a/none/tests/faultstatus.c +++ b/none/tests/faultstatus.c @@ -190,7 +190,9 @@ int main() return 0; } +static volatile s_zero; + static int zero() { - return 0; + return s_zero; } |
|
From: Paul F. <pa...@so...> - 2021-11-23 21:01:50
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=01e05ea81c4886636b44545eb501139b76d5dc7a commit 01e05ea81c4886636b44545eb501139b76d5dc7a Author: Paul Floyd <pj...@wa...> Date: Tue Nov 23 21:58:45 2021 +0100 Disable auxv PAGESIZES workaround on FreeBSD 13 Leaving it in place for 11 (which is now EOL) and 12 - not woth the complexity for them. Improve comment for supporession. Also add a pointer to the illumos source web page for lwp_unlock_mutex in case the syswrap ever needs improving. Diff: --- coregrind/m_initimg/initimg-freebsd.c | 15 +++++++++++++-- coregrind/m_syswrap/syswrap-solaris.c | 2 ++ freebsd.supp | 6 +++++- 3 files changed, 20 insertions(+), 3 deletions(-) diff --git a/coregrind/m_initimg/initimg-freebsd.c b/coregrind/m_initimg/initimg-freebsd.c index d19186a42c..71fb8add17 100644 --- a/coregrind/m_initimg/initimg-freebsd.c +++ b/coregrind/m_initimg/initimg-freebsd.c @@ -578,7 +578,7 @@ Addr setup_client_stack( void* init_sp, /* --- auxv --- */ auxv = (struct auxv *)ptr; *client_auxv = (UInt *)auxv; -#if defined(VGP_x86_freebsd) +#if defined(VGP_x86_freebsd) && (VGO_freebsd <= FREEBSD_13) int* pagesizes = NULL; #endif @@ -610,6 +610,17 @@ Addr setup_client_stack( void* init_sp, * copies out the data for a sysctl sees this discrepancy and * sets an ENOMEM error. So guest execution doesn't even get past * executing the dynamic linker. + * + * This was fixed in the kernel in May 2020, see + * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246215 + * + * That means this workaround is not needed for + * FreeBSD 13 or later, any version + * FreeBSD 12 1201515 and later + * FreeBSD 11 1104501 and later + * + * Because this is rather complicated I've just disabled the hack + * for 13 and later */ for (; orig_auxv->a_type != AT_NULL; auxv++, orig_auxv++) { @@ -649,7 +660,7 @@ Addr setup_client_stack( void* init_sp, // case AT_CANARYLEN: // case AT_EXECPATH: // case AT_CANARY: -#if defined(VGP_x86_freebsd) +#if defined(VGP_x86_freebsd) && (VGO_freebsd <= FREEBSD_13) case AT_PAGESIZESLEN: if (!VG_(is32on64)()) { VG_(debugLog)(2, "initimg", diff --git a/coregrind/m_syswrap/syswrap-solaris.c b/coregrind/m_syswrap/syswrap-solaris.c index d1ce0fd6bb..ea46073427 100644 --- a/coregrind/m_syswrap/syswrap-solaris.c +++ b/coregrind/m_syswrap/syswrap-solaris.c @@ -10639,6 +10639,8 @@ PRE(sys_lwp_mutex_register) PRE(sys_lwp_mutex_unlock) { /* int lwp_mutex_unlock(lwp_mutex_t *lp); */ + /* see https://github.com/illumos/illumos-gate/blob/master/usr/src/uts/common/syscall/lwp_sobj.c#L3137-L3138 + * (illumos, obviously) */ vki_lwp_mutex_t *lp = (vki_lwp_mutex_t*)ARG1; PRINT("sys_lwp_mutex_unlock ( %#lx )", ARG1); PRE_REG_READ1(int, "lwp_mutex_unlock", lwp_mutex_t *, lp); diff --git a/freebsd.supp b/freebsd.supp index b86b800d80..10d4a10454 100644 --- a/freebsd.supp +++ b/freebsd.supp @@ -1,5 +1,9 @@ # Suppressions for FreeBSD / Memcheck -#This is a workaround for a bug in rtld + +# This is a workaround for a bug in rtld / sysctl hw.pagesizes +# it was fixed in May 2020 in the kernel +# removing it means either waiting for 12-RELEASE EOL +# or some tricky kernel detection in configure.ac { MEMCHECK-RTLD-32ON64 Memcheck:Addr4 |
|
From: Ambalu, R.
|
Dear community, I noticed lately that I'm no longer able to run valgrind on my processes that import the latest pyarrow ( python ). I think its due to an Avx512 instruction that they recently added, which valgrind doesn't support. I just tried compiling trunk version of valgrind to see if its in but I still seem to hit the error with the latest build. This is the error from valgrind: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x8 0x6F 0x44 0x24 0xA 0xC7 0x43 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==32035== valgrind: Unrecognised instruction at address 0x1085ea85. ==32035== at 0x1085EA85: arrow::compute::internal::RegisterScalarAggregateSumAvx512(arrow::compute::FunctionRegistry*) (in /home/ra7293/user/hfalgo_csp/.venvs/PY36/build_tools_venv/lib/libarrow.so.100.1.0) ==32035== by 0x1067967C: arrow::compute::GetFunctionRegistry() (in /home/ra7293/user/hfalgo_csp/.venvs/PY36/build_tools_venv/lib/libarrow.so.100.1.0) ==32035== by 0x51CCDF0F: __pyx_pw_7pyarrow_8_compute_16FunctionRegistry_1__init__(_object*, _object*, _object*) (in /home/ra7293/user/hfalgo_csp/.venvs/PY36/build_tools_venv/lib/python3.6/site-packages/pyarrow/_compute.cpython-36m-x86_64-linux-gnu.so) Please let me know if this is something that can be added and if you need any more information. I love valgrind and use it regularly, I really hope to see this added as soon as possible. Thank you for this awesome tool! - Rob DISCLAIMER: This e-mail message and any attachments are intended solely for the use of the individual or entity to which it is addressed and may contain information that is confidential or legally privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and permanently delete this message and any attachments. |
|
From: Julian S. <jse...@gm...> - 2021-11-23 10:33:07
|
Greetings developers, A couple of us thought that it would be nice to have, from time to time, a group video call for developers. So that we can talk, discuss the status of work, problems, who needs help with what, and generally just associate faces and personalities with names. The call is at Fri 26 Nov, 1700 UTC / 1800 CET / 0900 PST. You can join from your web browser (meaning, it runs within the browser) at https://meet.jit.si/ValgrindDevMeeting. See you there! J |