From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 08E423858C30; Fri, 16 Feb 2024 05:40:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 08E423858C30
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1708062027;
	bh=LnDBPhkT1Byd8u7oOT31d5AHG39N/BpoqDRMJpJizQs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=I9kKMYJRo7IP0YzvEhsQHGbgzGK8joV25JthlSMC8TsHQyQ6rCh2yhsfkl8OPPnXW
	 //MH0JefbY/2EU2thsok2e/PXP+be5Axbfm67gNTyerOjwmNWT0dZZP/nxjEU5wcuc
	 BTXyUvEU2Q63DLxkrsm8ZTfeMy7ujE//fPc0Yiq0=
From: "adrian.ratiu at collabora dot com"
 <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/30453] gdbserver cannot set breakpoints when 
 /proc/pid/mem is not writable
Date: Fri, 16 Feb 2024 05:40:26 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: server
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adrian.ratiu at collabora dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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: <bug-30453-4717-HsA0rk3b4o@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30453-4717@http.sourceware.org/bugzilla/>
References: <bug-30453-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30453

--- Comment #17 from Adrian Ratiu <adrian.ratiu at collabora dot com> ---
(In reply to Tom Tromey from comment #15)=20
> As a workaround you can use an old gdbserver and a new gdb.
> I believe this should work fine.  It's maybe only mildly
> inconvenient if you use the gdbserver pipe feature
> ("target remote | gdbserver - ...")

Thanks, I also tested gdbserver 9.2 together with gdb 13.1 and it works as =
well
for the basic use cases I'm interested in.

So basically I have 3 solutions:

1. Apply the kernel patch to relax ChromeOS /proc/pid/mem policy.

2. Apply the gdbserver patch to fallback to ptrace R/W.

3. Use old gdbserver with newer gdb.

If neither of the upstreams don't want the respective patches, then maybe t=
he
path forward is to carry a change/patch for points 2 or 3 in the CrOS gdb
ebuild?

At least that would give us a functional debugger without forcing the upstr=
eams
to accept a patch they don't want :)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=