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 breakpoints/26544] linespec.c:3233: internal-error: void decode_line_full (): Assertion `result.size () == 1 || canonical->pre_expanded' failed. Date: Thu, 27 Aug 2020 09:10:11 +0000 [thread overview] Message-ID: <bug-26544-4717-d8CJe5dqWJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26544-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26544 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- Message improved: ... diff --git a/gdb/linespec.c b/gdb/linespec.c index 4a634e3aff..75ed8a9971 100644 --- a/gdb/linespec.c +++ b/gdb/linespec.c @@ -3230,6 +3230,10 @@ decode_line_full (const struct event_location *loca tion, int flags, location); state = PARSER_STATE (&parser); + if (result.size () == 0) + throw_error (NOT_SUPPORTED_ERROR, _("Location %s not available"), + event_location_to_string ((struct event_location *)location)) ; + gdb_assert (result.size () == 1 || canonical->pre_expanded); canonical->pre_expanded = 1; ... Such that we have: ... $ gdb a.out Reading symbols from a.out... (gdb) b main:L1 Location main:L1 not available (gdb) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-27 9:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-27 7:26 [Bug breakpoints/26544] New: " vries at gcc dot gnu.org 2020-08-27 8:11 ` [Bug breakpoints/26544] " vries at gcc dot gnu.org 2020-08-27 8:14 ` vries at gcc dot gnu.org 2020-08-27 8:33 ` vries at gcc dot gnu.org 2020-08-27 9:10 ` vries at gcc dot gnu.org [this message] 2020-08-27 11:52 ` vries at gcc dot gnu.org 2020-08-27 11:54 ` vries at gcc dot gnu.org 2020-08-27 12:01 ` vries at gcc dot gnu.org 2020-08-28 10:02 ` cvs-commit at gcc dot gnu.org 2020-08-28 10:03 ` vries at gcc dot gnu.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-26544-4717-d8CJe5dqWJ@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).