public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/24694] FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=1: follow_exec_mode=same: continue across exec that changes architecture (Couldn't get registers: No such process) Date: Fri, 04 Dec 2020 13:18:39 +0000 [thread overview] Message-ID: <bug-24694-4717-9oX5qIPBmx@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24694-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24694 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #11 from Pedro Alves <palves at redhat dot com> --- > So the ptrace resume on the other thread fails with > Couldn't get registers: No such process. > But I also think we should handle the situation better. When resuming > multiple threads and one of them fails with "no such process", we should > probably print a warning but carry on, not abort the continue. Note we already ignore failures to resume when the thread disappears. See linux_resume_one_lwp -> check_ptrace_stopped_lwp_gone in both gdb and gdbserver. And also, gdbserver ignores ESRCH when reading registers. See linux-low.cc:regsets_fetch_inferior_registers: else if (errno == ESRCH) { /* At this point, ESRCH should mean the process is already gone, in which case we simply ignore attempts to read its registers. */ } Native gdb is missing the equivalent. Unfortunately, on the native side, the code calling PTRACE_GETREGS / PTRACE_GETREGSET / PTRACE_SETREGS / PTRACE_SETREGSET is dispersed throughout all architecture ports. Does the issue trigger with gdbserver? I'd assume not. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-04 13:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24694-4717@http.sourceware.org/bugzilla/> 2020-05-17 9:10 ` vries at gcc dot gnu.org 2020-07-21 14:41 ` vries at gcc dot gnu.org 2020-12-01 2:57 ` simark at simark dot ca 2020-12-01 3:03 ` simark at simark dot ca 2020-12-01 3:42 ` simark at simark dot ca 2020-12-04 13:18 ` palves at redhat dot com [this message] 2020-12-04 17:59 ` simark at simark dot ca 2020-12-11 0:56 ` cvs-commit at gcc dot gnu.org 2020-12-11 0:57 ` simark at simark dot ca
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-24694-4717-9oX5qIPBmx@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).