public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit Date: Tue, 16 Jan 2024 07:35:21 +0000 [thread overview] Message-ID: <bug-29833-4717-zz37QqESb9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29833-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29833 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|gdb |testsuite Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |15.1 --- Comment #15 from Tom de Vries <vries at gcc dot gnu.org> --- Fixed by: ... commit aae436c54a514d43ae66389f2ddbfed16ffdb725 Author: Simon Marchi <simon.marchi@efficios.com> Date: Mon Jan 15 16:23:42 2024 +0000 gdb/testsuite: remove spurious $ in save_vars ... -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-16 7:35 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 7:19 [Bug gdb/29833] New: " vries at gcc dot gnu.org 2022-11-30 8:11 ` [Bug gdb/29833] " vries at gcc dot gnu.org 2022-11-30 9:45 ` vries at gcc dot gnu.org 2022-11-30 12:50 ` simark at simark dot ca 2022-12-01 9:50 ` vries at gcc dot gnu.org 2022-12-01 10:59 ` vries at gcc dot gnu.org 2022-12-01 11:18 ` vries at gcc dot gnu.org 2023-01-06 18:05 ` vries at gcc dot gnu.org 2023-01-07 17:42 ` vries at gcc dot gnu.org 2023-01-09 14:53 ` vries at gcc dot gnu.org 2023-01-09 14:53 ` vries at gcc dot gnu.org 2023-01-10 10:43 ` vries at gcc dot gnu.org 2023-01-10 14:00 ` vries at gcc dot gnu.org 2023-03-11 15:03 ` vries at gcc dot gnu.org 2024-01-15 9:20 ` vries at gcc dot gnu.org 2024-01-16 7:35 ` vries at gcc dot gnu.org [this message]
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-29833-4717-zz37QqESb9@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).