From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 808123858003; Fri, 9 Jul 2021 18:57:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 808123858003 From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/28065] FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem (print global_var after writing again, inf=1, iter=354) Date: Fri, 09 Jul 2021 18:57:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2021 18:57:08 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28065 --- Comment #16 from Tom de Vries --- (In reply to Pedro Alves from comment #14) > This is brilliant work, Tom. Thanks for doing all this. >=20 Np :) > In the standalong reproducer, you're missing a close(fd) at the end of > get_global_var, but even with that it reproduces for me too. >=20 Ack, thanks. > It looks like a kernel bug to me off hand, are you thinking otherwise? I'm not sure. I made the standalone reproducer to show to the kernel people such that they can answer that question ;) I read your comment about mem_rw, and looked at the code, and that seems to make sense, but ... not my expertise, so I easily could be overlooking something. FWIW, I found in https://man7.org/linux/man-pages/man5/proc.5.html : ... /proc/[pid]/task (since Linux 2.6.0) ... In a multithreaded process, the contents of the /proc/[pid]/task directory are not available if the main thread has already terminated (typically by calling pthread_exit(3)). ... So, I guess it's possible we get the "unsupported" answer. --=20 You are receiving this mail because: You are on the CC list for the bug.=