public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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, 11 Dec 2020 00:56:51 +0000 [thread overview] Message-ID: <bug-24694-4717-U5AhOx3vO5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24694-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24694 --- Comment #13 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Simon Marchi <simark@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4483a8e72ad265b5d428899d384bf190db071759 commit 4483a8e72ad265b5d428899d384bf190db071759 Author: Simon Marchi <simon.marchi@efficios.com> Date: Thu Dec 10 19:55:56 2020 -0500 gdb/testsuite: fix race condition in gdb.multi/multi-arch-exec.exp That test fails intermittently for me. The problem is a race condition between the exec syscall and GDB resuming threads. The initial situation is that we have two threads, let's call them "leader" and "other". Leader is the one who is going to do the exec. We stop at the breakpoint on the all_started function, so both threads are stopped. When resuming, GDB resumes leader first and other second. However, between resuming the two threads, leader has time to run and do its exec, making other disappear. When GDB tries to resume other, it is ino longer there. We get some "Couldn't get registers: No such process." messages, and the state is a bit messed up. The issue can be triggered consistently by adding a small delay after the resume syscall: diff --git a/gdb/inf-ptrace.c b/gdb/inf-ptrace.c index d5a062163c7..9540339a9da 100644 --- a/gdb/inf-ptrace.c +++ b/gdb/inf-ptrace.c @@ -308,6 +308,8 @@ inf_ptrace_target::resume (ptid_t ptid, int step, enum gdb_signal signal) gdb_ptrace (request, ptid, (PTRACE_TYPE_ARG3)1, gdb_signal_to_host (signal)); if (errno != 0) perror_with_name (("ptrace")); + for (int i = 0 ; i < 100; i++) + usleep (10000); } /* Wait for the child specified by PTID to do something. Return the This patch is about fixing the test to avoid this, since the test is not about testing this particular corner case. Handling of multi-threaded program doing execs should be improved too, but that's not the goal of this patch. Fix it by adding a synchronization point in the test to make sure both threads were resumed by GDB before doing the exec. I added two pthread_barrier_wait calls in each thread (for a total of three). I think adding one call in each thread would not be enough, because this could happen: - both threads reach the first barrier - the "other" thread is scheduled so has time to run and hit the second barrier - the "leader" thread hits the all_started function breakpoint, causing both threads to be stopped by GDB - GDB resumes the "leader" thread - Since the "other" thread has already reached the second barrier, the "leader" thread is free to run past its second barrier and do the exec, while GDB still hasn't resumed the second one By adding two barrier calls in each thread, I think we are good. The test passes consistently for me, even with the artificial delay added. gdb/testsuite/ChangeLog: PR gdb/24694 * gdb.multi/multi-arch-exec.c (thread_start, main): Add barrier calls. Change-Id: I25c8ea9724010b6bf20b42691c716235537d0e27 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-11 0:56 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 2020-12-04 17:59 ` simark at simark dot ca 2020-12-11 0:56 ` cvs-commit at gcc dot gnu.org [this message] 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-U5AhOx3vO5@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).