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/30820] DAP GDB: Getting an error when bypassing "source" to breakpoint
Date: Mon, 04 Sep 2023 17:53:20 +0000 [thread overview]
Message-ID: <bug-30820-4717-XLiQcnJsAd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30820-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30820
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-09-04
CC| |tromey at sourceware dot org
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
set_breakpoint does:
specs = [_rewrite_src_breakpoint(source=source, **bp) for bp in
breakpoints]
but if 'bp' has a 'source' entry then this will cause the clash.
While we should probably fix this, at the same time I'm not sure this
is expected. setBreakpoints takes an array of SourceBreakpoint objects,
not Breakpoint objects. And SourceBreakpoint doesn't mention "source".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-04 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 8:20 [Bug dap/30820] New: Error " artem.sokolovskii at qt dot io
2023-09-04 8:36 ` [Bug dap/30820] DAP GDB: Getting an error " artem.sokolovskii at qt dot io
2023-09-04 17:53 ` tromey at sourceware dot org [this message]
2023-09-05 8:00 ` artem.sokolovskii at qt dot io
2023-09-05 13:00 ` tromey at sourceware dot org
2023-09-05 13:55 ` artem.sokolovskii at qt dot io
2023-09-12 16:37 ` cvs-commit at gcc dot gnu.org
2023-09-12 16:37 ` 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-30820-4717-XLiQcnJsAd@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: link
Be 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).