From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 35DC0386D606; Thu, 15 Feb 2024 19:13:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 35DC0386D606 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708024406; bh=v9gGwLvom1qKIYLLinqyi3gwXMQAxFO3uOd8rDeQplo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OIM8NwEyBMCVyxaraFbcz+5ddTxl02V1cscmL8BhXhAJg2SMdovi9curhK+aFJzmF fsiiZoCsq9AKXRUaQrCnI3YY++J79DJFJ2L0bLYF3vjH16MywlNIqzLJbynhkYraER zHGMJsNSjBECwj2I4lAKVxAWXyoyqUlkNysFxhkg= From: "adrian.ratiu at collabora dot com" To: gdb-prs@sourceware.org Subject: [Bug server/30453] gdbserver cannot set breakpoints when /proc/pid/mem is not writable Date: Thu, 15 Feb 2024 19:13:25 +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: 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=3D30453 --- Comment #11 from Adrian Ratiu --- > for example after writing it I noticed that gdb/linux-nat.c contains proc= _mem_file_is_writable () which does something similar, maybe I could reuse = that logic? Hm.. actually I'm not that certain we can reuse that logic because it's wri= ting to /proc/self/mem, which won't work for gdbserver IIUC. --=20 You are receiving this mail because: You are on the CC list for the bug.=