From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 831743858033; Tue, 11 Jul 2023 18:46:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 831743858033 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689101164; bh=qpHzqukeIBhK4xW2eGcQLP39rDVe0thl+Fe494Y8GXc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yOzBkCT/yc1j8vZdhl/OML7uCYOJcbUL1eVFdxRHQ3d7VBTM4E8HnwgZ6YsaeLvJH HkyE28IFjp1hUXmSakJlJjch1k/+ondQgX34TLX2vk5CukUmUGTrus9mHn/Db82ssG ssLCBjyouvdzFM3XwsuYyeCpKxkDmkA8QvoffOX8= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Tue, 11 Jul 2023 18:46:03 +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: tromey at sourceware 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 #19 from Tom Tromey --- Whatever we do we'll need a new request on the valgrind side. If it implemented vFile you could use "target remote | ssh mumble valgrind" I think the machine-id is documented that way for privacy, not=20 security -- there's no consequence if someone finds out your machine-id. So, we could maybe just ignore that text. Or, we could use an existing thing like the CRC that gdbserver already uses, or SHA1. That seems like it would also be fine. The main thing is we have to document the procedure somehow. Not sure what to use on Windows. I'm mildly worried that there is some scenario where the ids clash by accident, or where /tmp is shared but nothing else is. May not really be worth worrying about. --=20 You are receiving this mail because: You are on the CC list for the bug.=