public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at palves dot net" <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: Tue, 16 May 2023 18:17:24 +0000 [thread overview] Message-ID: <bug-30453-4717-qonqcvWpEf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30453-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30453 --- Comment #2 from Pedro Alves <pedro at palves dot net> --- What's the point of setting up a system such that a debugger can't write to inferior memory using /proc/pid/mem, but it can write via ptrace? That gives you no extra protection. I think the right fix is to just make it so that the kernel allows writes if the calling process has ptrace permissions over the target pid, even if it prohibits other processes from writing. The workaround on the gdb side was for very old kernels, and for example will not work with non-stop mode, and of course does not support writing memory while threads are running (such as setting breakpoints), which was the point of switching to /proc/pid/mem all the time. I would hope that with recent enough kernels things would just work reasonably. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-16 18:17 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-16 16:00 [Bug server/30453] New: " manojgupta at google dot com 2023-05-16 16:02 ` [Bug server/30453] " manojgupta at google dot com 2023-05-16 18:17 ` pedro at palves dot net [this message] 2023-05-16 18:24 ` manojgupta at google dot com 2023-05-16 20:00 ` pedro at palves dot net 2023-05-16 20:13 ` manojgupta at google dot com 2023-05-17 19:03 ` manojgupta at google dot com 2023-05-18 11:50 ` pedro at palves dot net 2024-02-15 19:06 ` adrian.ratiu at collabora dot com 2024-02-15 19:07 ` adrian.ratiu at collabora dot com 2024-02-15 19:07 ` adrian.ratiu at collabora dot com 2024-02-15 19:13 ` adrian.ratiu at collabora dot com 2024-02-15 20:09 ` pedro at palves dot net 2024-02-15 20:18 ` pedro at palves dot net 2024-02-15 20:18 ` pedro at palves dot net 2024-02-16 2:54 ` tromey at sourceware dot org 2024-02-16 5:29 ` adrian.ratiu at collabora dot com 2024-02-16 5:40 ` adrian.ratiu at collabora dot com 2024-02-16 9:47 ` adrian.ratiu at collabora dot com 2024-02-16 17:33 ` tromey at sourceware dot org 2024-02-16 17:53 ` pedro at palves dot net 2024-02-16 17:56 ` pedro at palves dot net 2024-02-16 18:10 ` adrian.ratiu at collabora dot com 2024-02-16 18:17 ` pedro at palves dot net 2024-02-16 20:53 ` mark at klomp dot org 2024-02-16 21:36 ` pedro at palves dot net 2024-02-16 21:38 ` pedro at palves dot net 2024-02-16 21:57 ` tromey at sourceware dot org 2024-02-22 13:28 ` adrian.ratiu at collabora dot com 2024-02-23 17:01 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30453-4717-qonqcvWpEf@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).