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 dap/31217] dap throws exception when trying to rerun session Date: Mon, 22 Jan 2024 16:00:07 +0000 [thread overview] Message-ID: <bug-31217-4717-ZNtpaYiCZ4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31217-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31217 --- Comment #9 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=46bdb641642d20307521f5db2e1f1c7dcc49d5a7 commit 46bdb641642d20307521f5db2e1f1c7dcc49d5a7 Author: Tom Tromey <tromey@adacore.com> Date: Wed Jan 10 12:51:10 2024 -0700 Handle EOF more gracefully in DAP A user pointed out that gdb will print a Python exception when it gets an EOF in DAP mode. And, it turns out that an EOF like this also causes gdb not to exit. This is due to the refactoring that moved the JSON reader to its own thread -- previously this caused an exception to propagate and cause an exit, but now it just leaves the reader hung. This patch fixes these problems by arranging to handle EOF more gracefully. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31217 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-22 16:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-06 16:02 [Bug dap/31217] New: " asn at samba dot org 2024-01-08 23:23 ` [Bug dap/31217] " tromey at sourceware dot org 2024-01-09 8:07 ` asn at samba dot org 2024-01-09 8:08 ` asn at samba dot org 2024-01-09 17:02 ` tromey at sourceware dot org 2024-01-09 20:36 ` asn at samba dot org 2024-01-09 21:20 ` asn at samba dot org 2024-01-10 19:01 ` tromey at sourceware dot org 2024-01-10 20:09 ` tromey at sourceware dot org 2024-01-22 16:00 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-22 16:00 ` 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-31217-4717-ZNtpaYiCZ4@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).