public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug dap/31217] dap throws exception when trying to rerun session Date: Wed, 10 Jan 2024 19:01:00 +0000 [thread overview] Message-ID: <bug-31217-4717-mQpO5lpuoN@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 #7 from Tom Tromey <tromey at sourceware dot org> --- Thank you for the reproducer. That makes this very easy! I think this is just a generic error when shutting down. In particular I think nvim is ending the connection, then gdb is printing this exception from its reader. gdb should shut down more cleanly in this case. Also I see that nvim seems to send a full path name in its breakpoint request, so my session wouldn't hit the breakpoint because the path name was not found in the executable. That confused me for a bit but recompiling cleared it up. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-10 19:01 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 [this message] 2024-01-10 20:09 ` tromey at sourceware dot org 2024-01-22 16:00 ` cvs-commit at gcc dot gnu.org 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-mQpO5lpuoN@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).