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
(6) |
|
2
(6) |
3
(9) |
4
(4) |
5
(1) |
6
|
7
|
8
|
|
9
|
10
(2) |
11
(1) |
12
(2) |
13
(4) |
14
(6) |
15
(8) |
|
16
(9) |
17
(5) |
18
(13) |
19
(6) |
20
(15) |
21
(17) |
22
(19) |
|
23
(2) |
24
(4) |
25
(2) |
26
(10) |
27
(6) |
28
(9) |
29
(3) |
|
30
|
|
|
|
|
|
|
|
From: Nicholas N. <n.n...@gm...> - 2023-04-16 21:15:32
|
Hi, My plans for the release: - I have one more significant improvement to `cg_annotate` to come, which will add merge and diff capability to it, in a way that is better than the merge/diff capability provided by `cg_merge` and `cg_diff`. - I need to update the Cachegrind docs and the NEWS file for all the changes I've made. I know these will be happening late in the release cycle, but because it's all Python code it should require less testing. The likelihood of platform-specific differences in behaviour is much lower than in most other code within Valgrind. Nick On Sat, 15 Apr 2023 at 12:07, Mark Wielaard <ma...@kl...> wrote: > An RC1 tarball for 3.21.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2 > (md5sum = a3c7eeff47262cecdf5f1d68b38710b7) > (sha1sum = 46fc5898415001e045abc1b4e2909a41144ed9c4) > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2.asc > > Please give it a try in configurations that are important for you and > report any problems you have, either on this mailing list, or > (preferably) via our bug tracker at > https://bugs.kde.org/enter_bug.cgi?product=valgrind > > There are still some patches being reviewed and a RC2 will appear end > of next week. If nothing critical emerges after that, a final release > will happen on Friday 28 April. > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Paul F. <pj...@wa...> - 2023-04-16 21:04:06
|
On 15-04-23 04:06, Mark Wielaard wrote: > An RC1 tarball for 3.21.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2 > (md5sum = a3c7eeff47262cecdf5f1d68b38710b7) > (sha1sum = 46fc5898415001e045abc1b4e2909a41144ed9c4) > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2.asc Illumos builds OK now from git HEAD. Test 3 macOS 10.13, a bit like Solaris 11.3, no pipe2 vgdb.c:91:32: warning: format specifies type 'long' but the argument has type '__darwin_suseconds_t' (aka 'int') [-Wformat] sprintf(ptr, ".%6.6ld ", dbgtv.tv_usec); ~~~~~~ ^~~~~~~~~~~~~ %6.6d /usr/include/secure/_stdio.h:47:56: note: expanded from macro 'sprintf' __builtin___sprintf_chk (str, 0, __darwin_obsz(str), __VA_ARGS__) ^~~~~~~~~~~ vgdb.c:1145:8: warning: implicit declaration of function 'pipe2' is invalid in C99 [-Wimplicit-function-declaration] if (pipe2 (pipefd, O_CLOEXEC) == -1) { Builds OK from git HEAD. Test 4 Alpine (musl) Builds OK == 614 tests, 102 stderr failures, 27 stdout failures, 1 stderrB failure, 2 stdoutB failures, 4 post failures == Test 5 FreeBSD No problems same as nightly == 796 tests, 2 stderr failures, 1 stdout failure, 1 stderrB failure, 1 stdoutB failure, 0 post failures == A+ Paul |
|
From: Philippe W. <phi...@sk...> - 2023-04-16 12:36:01
|
On Sun, 2023-04-16 at 02:28 +0200, Mark Wielaard wrote: > > The problem is solved by giving an absolute path for the remote exec-file: > > (gdb) set remote exec-file /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > > It doesn't need to be an absolute path, it can also be a relative path > like: set remote exec-file ./sleepers > > Note that this is similar to how valgrind normally resolves > executables. Effectively. I was confused as GDB does not use the PATH. E.G.: philippe@md:gdbserver_tests$ valgrind -q sleepers valgrind: sleepers: command not found philippe@md:gdbserver_tests$ gdb -q sleepers Loaded DUEL.py 0.9.6, high level data exploration language Reading symbols from sleepers... (gdb) start Temporary breakpoint 1 at 0x16fc: file sleepers.c, line 138. So, it looks like in multi mode, I put my brain in "GDB mode". where absolute (or relative path) is not needed :). > > > > Not too sure what is going wrong/what I am doing wrong ... > > Nothing. There is something about sleepers that causes this. It also > happens for me. I'll try to debug it. But it works when you give vgdb > -d -d debug options... Humph, race condition/timing related bugs are hard to debug :(. Thanks Philippe |
|
From: Paul F. <pa...@so...> - 2023-04-16 12:29:07
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=0bc69d40a5021b158804fb4f39592596333f7013 commit 0bc69d40a5021b158804fb4f39592596333f7013 Author: Paul Floyd <pj...@wa...> Date: Sun Apr 16 14:27:04 2023 +0200 illunmos: fix configure scf_handle_bind check Migration to GCC 10 changes to 64bit load, see https://github.com/omniosorg/omnios-extra/blob/master/build/valgrind/patches/libscf.patch Diff: --- configure.ac | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index a886d0deaa..a439ec85d9 100755 --- a/configure.ac +++ b/configure.ac @@ -4513,11 +4513,11 @@ if test "X$VGCONF_ARCH_PRI" = "Xamd64"; then else libscf=/usr/lib/libscf.so.1 fi -if ! $DIS_PATH -F scf_handle_bind $libscf | grep -q 0x526570; then +if ! $DIS_PATH -F scf_handle_bind $libscf | grep -q -E '0x(4d01)?526570'; then AC_MSG_WARN([Function `scf_handle_bind' does not contain repository cache protocol version.]) AC_MSG_ERROR([Cannot determine version of the repository cache protocol.]) fi -hex=$( $DIS_PATH -F scf_handle_bind $libscf | sed -n 's/.*0x526570\(..\).*/\1/p' ) +hex=$( $DIS_PATH -F scf_handle_bind $libscf | perl -pe '($_) = /0x(?:4d01)?526570(\d{2}),/' ) if test -z "$hex"; then AC_MSG_WARN([Version of the repository cache protocol is empty?!]) AC_MSG_ERROR([Cannot determine version of the repository cache protocol.]) |
|
From: Paul F. <pj...@wa...> - 2023-04-16 11:28:40
|
On 15-04-23 04:06, Mark Wielaard wrote: > An RC1 tarball for 3.21.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2 > (md5sum = a3c7eeff47262cecdf5f1d68b38710b7) > (sha1sum = 46fc5898415001e045abc1b4e2909a41144ed9c4) > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2.asc > > Please give it a try in configurations that are important for you and > report any problems you have, either on this mailing list, or > (preferably) via our bug tracker at > https://bugs.kde.org/enter_bug.cgi?product=valgrind Test 2, Illumos (OpenIndiana 22.10 with latest pkg update) Configure failure related to this check if ! $DIS_PATH -F scf_handle_bind $libscf | grep -q 0x526570; then The constant used now seems to be 0x4d0152657015 Just dropping the 0x seems to work. A+ Paul |
|
From: Mark W. <ma...@so...> - 2023-04-16 11:19:21
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=932332e660a458e51068937130d557fb4acc6630 commit 932332e660a458e51068937130d557fb4acc6630 Author: Mark Wielaard <ma...@kl...> Date: Sun Apr 16 13:15:03 2023 +0200 Use pipe in vgdb if system doesn't have pipe2 Add a configure check for pipe2. If it isn't available use pipe and fcntl F_SETFD FD_CLOEXEC in vgdb.c. https://bugs.kde.org/show_bug.cgi?id=468556 Diff: --- NEWS | 1 + configure.ac | 1 + coregrind/vgdb.c | 17 +++++++++++++++++ 3 files changed, 19 insertions(+) diff --git a/NEWS b/NEWS index a8ab817e17..6af3169d5a 100644 --- a/NEWS +++ b/NEWS @@ -151,6 +151,7 @@ are not entered into bugzilla tend to get forgotten about or ignored. 467714 fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened 467839 Gdbserver: Improve compatibility of library directory name +468556 Build failure for vgdb n-i-bz FreeBSD rfork syscall fail with EINVAL or ENOSYS rather than VG_(unimplemented) To see details of a given bug, visit diff --git a/configure.ac b/configure.ac index 66437a8000..a886d0deaa 100755 --- a/configure.ac +++ b/configure.ac @@ -4820,6 +4820,7 @@ AC_CHECK_FUNCS([ \ memset \ mkdir \ mremap \ + pipe2 \ ppoll \ preadv \ preadv2 \ diff --git a/coregrind/vgdb.c b/coregrind/vgdb.c index c4a7042984..7ed9a8b2e9 100644 --- a/coregrind/vgdb.c +++ b/coregrind/vgdb.c @@ -1142,11 +1142,28 @@ int fork_and_exec_valgrind (int argc, char **argv, const char *working_dir, // We will use a pipe to track what the child does, // so we can report failure. int pipefd[2]; +#ifdef HAVE_PIPE2 if (pipe2 (pipefd, O_CLOEXEC) == -1) { err = errno; perror ("pipe2 failed"); return err; } +#else + if (pipe (pipefd) == -1) { + err = errno; + perror ("pipe failed"); + return err; + } else { + if (fcntl (pipefd[0], F_SETFD, FD_CLOEXEC) == -1 + || fcntl (pipefd[1], F_SETFD, FD_CLOEXEC) == -1) { + err = errno; + perror ("fcntl failed"); + close (pipefd[0]); + close (pipefd[1]); + return err; + } + } +#endif pid_t p = fork (); if (p < 0) { |
|
From: Paul F. <pj...@wa...> - 2023-04-16 07:44:33
|
On 04/15/23 04:06 AM, Mark Wielaard wrote: > An RC1 tarball for 3.21.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2 > (md5sum = a3c7eeff47262cecdf5f1d68b38710b7) > (sha1sum = 46fc5898415001e045abc1b4e2909a41144ed9c4) > https://sourceware.org/pub/valgrind/valgrind-3.21.0.RC1.tar.bz2.asc > First test, Solaris 11.3/ Build fails because pipe2 is not available. Also logged as https://bugs.kde.org/show_bug.cgi?id=468556 gcc -std=gnu11 -m64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -fomit-frame-pointer -m64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -fomit-frame-pointer -Wl,-M,/usr/lib/ld/map.noexstk -o valgrind valgrind-launcher-linux.o valgrind-m_debuglog.o gcc -std=gnu11 -m64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -fomit-frame-pointer -m64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -fomit-frame-pointer -o vgdb vgdb-vgdb.o vgdb-vgdb-invoker-solaris.o -lsocket Undefined first referenced symbol in file pipe2 vgdb-vgdb.o ld: fatal: symbol referencing errors collect2: error: ld returned 1 exit status gmake[3]: *** [vgdb] Error 1 gmake[3]: *** Waiting for unfinished jobs.... mv -f m_replacemalloc/.deps/libreplacemalloc_toolpreload_x86_solaris_a-vg_replace_malloc.Tpo m_replacemalloc/.deps/libreplacemalloc_toolpreload_x86_solaris_a-vg_replace_malloc.Po mv -f m_syswrap/.deps/libcoregrind_x86_solaris_a-syswrap-generic.Tpo m_syswrap/.deps/libcoregrind_x86_solaris_a-syswrap-generic.Po mv -f m_syswrap/.deps/libcoregrind_x86_solaris_a-syswrap-solaris.Tpo m_syswrap/.deps/libcoregrind_x86_solaris_a-syswrap-solaris.Po gmake[3]: Leaving directory `/export/home/paulf/test321/valgrind-3.21.0.RC1/coregrind' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/export/home/paulf/test321/valgrind-3.21.0.RC1/coregrind' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/export/home/paulf/test321/valgrind-3.21.0.RC1' gmake: *** [all] Error 2 A+ Paul |
|
From: Mark W. <ma...@kl...> - 2023-04-16 00:28:21
|
Hi Philippe, Thanks for testing things out. On Sat, Apr 15, 2023 at 07:58:16PM +0200, Philippe Waroquiers wrote: > I did some tests: > > philippe@md:gdbserver_tests$ gdb sleepers > GNU gdb (GDB) 14.0.50.20230402-git > Copyright (C) 2023 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-pc-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <https://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Loaded DUEL.py 0.9.6, high level data exploration language > Reading symbols from sleepers... > (gdb) set remote exec-file sleepers > (gdb) set sysroot / > (gdb) target extended-remote | vgdb --multi > Remote debugging using | vgdb --multi > (gdb) start > Temporary breakpoint 1 at 0x16fc: file sleepers.c, line 138. > Starting program: /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > valgrind: sleepers: command not found > syscall failed: No such file or directory > error opening /tmp/vgdb-pipe-shared-mem-vgdb-52790-by-philippe-on-md shared memory file > Remote communication error. Target disconnected.: Connection reset by peer. > (gdb) > > > > The problem is solved by giving an absolute path for the remote exec-file: > (gdb) set remote exec-file /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers It doesn't need to be an absolute path, it can also be a relative path like: set remote exec-file ./sleepers Note that this is similar to how valgrind normally resolves executables. $ valgrind sleepers valgrind: sleepers: command not found $ valgrind ./sleepers ==210626== Memcheck, a memory error detector ==210626== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==210626== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==210626== Command: ./sleepers ==210626== loops/sleep_ms/burn/threads_spec/affinity: 15 1000 0 BSBSBSBS 0 Brussels ready to sleep and/or burn London ready to sleep and/or burn Petaouchnok ready to sleep and/or burn main ready to sleep and/or burn Brussels finished to sleep and/or burn London finished to sleep and/or burn main finished to sleep and/or burn Petaouchnok finished to sleep and/or burn [...] > So, it looks like gdb knows the absolute path of the program to launch, but does not pass > it to valgrind. It might be possible to have the full path given to vgdb ? Yes that would be nice. Tom Tromey suggested we create a python plugin to do some of the things we are currently requiring the user to set by hand. Paul made a gdb alias that does some of it. I hope we will add a new target valgrind to gdb itself that will do that and that does the stdin/stdout redirecting (that is a current issue with target extended-remote | ... it will "eat" the stdin/out of the child process). > The vgdb --help output is missing the --valgrind and the --vargs in the OPTIONS summary: > OPTIONS are [--pid=<number>] [--vgdb-prefix=<prefix>] > [--wait=<number>] [--max-invoke-ms=<number>] > [--port=<portnr> > [--cmd-time-out=<number>] [-l] [-T] [-D] [-d] > [--multi] > > The vgdb --help is missing \n after the --vargs description: > --vargs everything that follows is an argument for valgrind. -l arg tells to show the list of running Valgrind gdbserver and then exit. Oops. Fixed. > For > --valgrind, pass the path to valgrind to use. If not specified, the system valgrind will be launched. > Wouldn't it better (if possible) to by default launch the valgrind found at the same place as where vgdb is found ? Yes that would be nice, I'll look into it. But I think that normally if vgdb is on the PATH then so will valgrind. > Finally, once giving an absolute remote exec-file and an absolute path to the valgrind to launch, > I cannot have it working: > gdb sleepers > GNU gdb (GDB) 14.0.50.20230402-git > Copyright (C) 2023 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-pc-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <https://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Loaded DUEL.py 0.9.6, high level data exploration language > Reading symbols from sleepers... > (gdb) set remote exec-file /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > (gdb) set sysroot / > (gdb) target extended-remote | vgdb --multi --valgrind=/home/philippe/valgrind/git/trunk_untouched/Inst/bin/valgrind > Remote debugging using | vgdb --multi --valgrind=/home/philippe/valgrind/git/trunk_untouched/Inst/bin/valgrind > (gdb) start > Temporary breakpoint 1 at 0x16fc: file sleepers.c, line 138. > Starting program: /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > ==100738== Memcheck, a memory error detector > ==100738== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==100738== Using Valgrind-3.21.0.RC1 and LibVEX; rerun with -h for copyright info > ==100738== Command: /home/philippe/valgrind/git/trunk_untouched/gdbserver_tests/sleepers > ==100738== > relaying data between gdb and process 100738 > syscall failed: Resource temporarily unavailable > error reading static buf readchar > syscall failed: Resource temporarily unavailable > readchar > no ack mode: unexpected buflen -1, buf > Unknown remote qXfer reply: 1 > (gdb) quit > > Not too sure what is going wrong/what I am doing wrong ... Nothing. There is something about sleepers that causes this. It also happens for me. I'll try to debug it. But it works when you give vgdb -d -d debug options... Cheers, Mark |
|
From: Mark W. <ma...@so...> - 2023-04-16 00:01:06
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=03d9229f0bdb28cf35e3bfc98010952594b091cd commit 03d9229f0bdb28cf35e3bfc98010952594b091cd Author: Mark Wielaard <ma...@kl...> Date: Sun Apr 16 01:55:48 2023 +0200 Fixup vgdb --help message The --valgrind and the --vargs were missingin the OPTIONS summary. A \n was missing after the --vargs description. Diff: --- coregrind/vgdb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/coregrind/vgdb.c b/coregrind/vgdb.c index 1cc37a3566..c4a7042984 100644 --- a/coregrind/vgdb.c +++ b/coregrind/vgdb.c @@ -1899,7 +1899,7 @@ void usage(void) " [--wait=<number>] [--max-invoke-ms=<number>]\n" " [--port=<portnr>\n" " [--cmd-time-out=<number>] [-l] [-T] [-D] [-d]\n" -" [--multi]\n" +" [--multi] [--valgrind=<valgrind-exe>] [--vargs ...]\n" " \n" " --pid arg must be given if multiple Valgrind gdbservers are found.\n" " --vgdb-prefix arg must be given to both Valgrind and vgdb utility\n" @@ -1915,7 +1915,7 @@ void usage(void) " gdbserver has not processed a command after number seconds\n" " --multi start in extended-remote mode, wait for gdb to tell us what to run\n" " --valgrind, pass the path to valgrind to use. If not specified, the system valgrind will be launched.\n" -" --vargs everything that follows is an argument for valgrind." +" --vargs everything that follows is an argument for valgrind.\n" " -l arg tells to show the list of running Valgrind gdbserver and then exit.\n" " -T arg tells to add timestamps to vgdb information messages.\n" " -D arg tells to show shared mem status and then exit.\n" |