From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 77FC73857B8E; Thu, 15 Jun 2023 13:13:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77FC73857B8E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1686834818; bh=3feXhShXmEN8gq8zyMuoO61NnNV+eDspCnUDVmycluU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bhbdjWl52Buu6W3B7oubL5da9VsFVqN0kpWYCraWZ9B4SAhuhT8iRXhj1wER6GgRW Ukq4OVCQyuFD1Jp4To4m8HTL584VelxpIfvvaaDzdNX6KAPrzu62dGwZQjF1FjJIGY anNZOqtIJ6GXHACHzWILaXra87dSP08UXqVbKq7s= From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Thu, 15 Jun 2023 13:13:37 +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: mark at klomp dot org 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: 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 --- Comment #5 from Mark Wielaard --- (In reply to Pedro Alves from comment #3) > Is there a reason "target valgrind" needs to be built-in to gdb? Paul (who doesn't seem to have a sourceware bugzilla account) tried to crea= te a user command for it and could completely make it work. In particular I beli= eve 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. > ... so that could go in some script put in the system gdbinit dir. Which dir is that and will that be autoloaded then? Another problem was tha= t it cannot be a normal autoload gdb script since those aren't loaded early enou= gh. Otherwise it could have been part of valgrind-monitor.py. See https://sourceforge.net/p/valgrind/mailman/message/37804321/ --=20 You are receiving this mail because: You are on the CC list for the bug.=