From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4A8E7385701E; Thu, 15 Jun 2023 15:41:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A8E7385701E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1686843660; bh=AzurFqQs71+BB3lIUnf/BB43DOBEEAMRlk2wVbdOe1I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mFFy5Im3iRMc1DpqRoLd938WfoCi+gN+4wMMfBOdWjwoNaOL723+fglHnSy4E3T07 eMKP9i0PUbFxdB++EyrVs75qDi8KkHKfLYVLpHgu+Q6v2dPS1jFPfZ4r0UV5QtTqif 7Qrt+70TEr/EdpV2+BWyLiqIYvqwToPeDzeMUewU= From: "pjfloyd at wanadoo dot fr" To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Thu, 15 Jun 2023 15:40:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pjfloyd at wanadoo dot fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30541 Paul Floyd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pjfloyd at wanadoo dot fr --- Comment #7 from Paul Floyd --- (In reply to Mark Wielaard from comment #5) > (In reply to Pedro Alves from comment #3) > > Is there a reason "target valgrind" needs to be built-in to gdb? >=20 > Paul (who doesn't seem to have a sourceware bugzilla account) tried to > create a user command for it and could completely make it work. In > particular I believe getting/setting the correct remote exec-file seemed > tricky and we would like the target to take arguments which are then added > to the remote program invocation. > See https://sourceforge.net/p/valgrind/mailman/message/37804321/ No account - fixed. What I was trying to do was just gdb myexe (gdb) start_vg [list of Valgrind arguments] As described in the e-mail above, there were two things that I found diffic= ult 1. Getting the exe name, which I solved with help from SO 2. Passing the commands on to valgrind - user-defined commands don't have a= $@ or $* like shells as far as I know I guess this would be easier in Python but I'm a bit useless at scripting. --=20 You are receiving this mail because: You are on the CC list for the bug.=