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 testsuite/31435] [gdb/testsuite] Runtest error running DAP tests Date: Mon, 18 Mar 2024 13:01:25 +0000 [thread overview] Message-ID: <bug-31435-4717-PxSmlN68fD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31435-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31435 --- Comment #11 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2518ce94704e54597bec273cafb090693b2de098 commit 2518ce94704e54597bec273cafb090693b2de098 Author: Tom Tromey <tromey@adacore.com> Date: Thu Mar 14 11:35:25 2024 -0600 Clear board_info entry after waiting for process When certain DAP tests are run in a certain order, dejagnu will throw an exception during shutdown. After adding many logging statements, I tracked this down to kill_wait_spawned_process not clearing the 'fileid' board_info entry, causing dejagnu to try to wait for the process a second time -- and fail. Tom de Vries then pointed out a second instance of this, which I tracked down to the same problem occurring when spawning gdbserver. This version of the patch fixes this by adding a new proc that can be used to clean up board_info after waiting for a process to exit. I'm not sure why this problem hasn't affected the test suite in the past. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31435 Approved-By: Andrew Burgess <aburgess@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-18 13:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 12:58 [Bug testsuite/31435] New: " vries at gcc dot gnu.org 2024-02-29 13:19 ` [Bug testsuite/31435] " vries at gcc dot gnu.org 2024-02-29 15:52 ` tromey at sourceware dot org 2024-03-14 16:37 ` tromey at sourceware dot org 2024-03-14 17:29 ` tromey at sourceware dot org 2024-03-14 17:57 ` tromey at sourceware dot org 2024-03-14 20:13 ` vries at gcc dot gnu.org 2024-03-15 9:15 ` vries at gcc dot gnu.org 2024-03-15 13:33 ` tromey at sourceware dot org 2024-03-15 13:38 ` tromey at sourceware dot org 2024-03-15 13:39 ` tromey at sourceware dot org 2024-03-15 14:30 ` tromey at sourceware dot org 2024-03-18 13:01 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-18 13:02 ` tromey at sourceware dot 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-31435-4717-PxSmlN68fD@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).