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/30471] Clean up DAP breakpoint reporting Date: Wed, 14 Jun 2023 16:27:03 +0000 [thread overview] Message-ID: <bug-30471-4717-UCcwVZiOzZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30471-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30471 --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I wonder if this is important at all. Multiple kinds of breakpoints could exist at a given location. So, differentiating that way doesn't always make sense; and anyway the stop event will hold the breakpoint IDs. For this case: elif _expected_stop is None: # FIXME what is even correct here _expected_stop = StopKinds.EXCEPTION ... maybe what we want is bug#13587, so we can report gdb's stop reason. This seems fine due to that "| string" clause at the end of the "reason" description. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-14 16:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-19 14:51 [Bug dap/30471] New: " tromey at sourceware dot org 2023-06-14 16:27 ` tromey at sourceware dot org [this message] 2023-12-12 14:58 ` [Bug dap/30471] " 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-30471-4717-UCcwVZiOzZ@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).