From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E97673858C5F; Tue, 11 Jul 2023 17:27:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E97673858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689096471; bh=ODasUeHALHNEE+rHjo7KIuX3fjgLayl3ITRliC6uDOo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WL+TFHykHLmHmjjdzhQ4nmiB5baRmWEP0Voly0m1BlfHFoMLbmaGk/N5bznlABQUr Vv8OO39IFfwUvxKRXMUUB1PR5AW9sZnMJhSN7/HqY/RlbJ5xkwlT4YJSPmyoWkSNev VCkHd9eoyV27Dd0pCemSYuUX+km4+c59r9Cy5dwA= From: "pedro at palves dot net" To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Tue, 11 Jul 2023 17:27:51 +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: pedro at palves dot net 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 #17 from Pedro Alves --- A simple alternative is for GDB to write a random hash to a mktemp file, and then target_fileio_open("target:/tmp/$that-tmp-file"), and then: - if the file opens succesfully, and, - the random string is the same as what gdb put in the file, then, the system is the same, and we can stop using target_fileio and open files directly. Well, at least the /tmp mount is the same, but, that seems like a good prox= y, isn't it? --=20 You are receiving this mail because: You are on the CC list for the bug.=