From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ED92D3858C74; Thu, 6 Jul 2023 16:44:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED92D3858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688661844; bh=GVmY98Q+6XxDaCvCWdcHe19V7vE1KJwf8DZ1aCAUkVo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ogdKAxGJlw9H/DfyX1C1+Ei8O/gKYP6jYig+XGGn7gWKhmx8KYFLNbJf2BZdqrlga apvLZHjI/EEsh8DuP88FsMqdPfZj2fNEr1e1ahF7e4aTH61jU2nH04JZKUVTJ6uR1E iHGZ2P8WPuGTM+Hfl463Dqmhk/oDG8t2AbhDaIuA= From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Thu, 06 Jul 2023 16:44:04 +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 #11 from Mark Wielaard --- (In reply to Tom Tromey from comment #10) > (In reply to Tom Tromey from comment #9) > > Maybe settings like sysroot should be per-target. > > That would enable complicated multi-target debug scenarios > > with multiple sysroots, and would solve this problem as well. >=20 > I found this code in remote.c today: >=20 > bool > remote_target::filesystem_is_local () > { > /* Valgrind GDB presents itself as a remote target but works > on the local filesystem: it does not implement remote get > and users are not expected to set a sysroot. To handle > this case we treat the remote filesystem as local if the > sysroot is exactly TARGET_SYSROOT_PREFIX and if the stub > does not support vFile:open. */ > ... >=20 > While this seems mildly questionable as a heuristic, at the > same time it may mean that there's nothing to do here for the > time being. Interesting. So that works if you don't set a sysroot so that it is just "target:". But it does this vFile:open probe which always produces: warning: remote target does not support file transfer, attempting to access files from local filesystem. Which makes it look like something is wrong. We really like to make the gdb/valgrind integration as clean as possible without the user getting all kinds of odd warnings. --=20 You are receiving this mail because: You are on the CC list for the bug.=