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] New: linespec.c:3233: internal-error: void decode_line_full (): Assertion `result.size () == 1 || canonical->pre_expanded' failed.
Date: Thu, 27 Aug 2020 07:26:58 +0000 [thread overview]
Message-ID: <bug-26544-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26544
Bug ID: 26544
Summary: linespec.c:3233: internal-error: void decode_line_full
(): Assertion `result.size () == 1 ||
canonical->pre_expanded' failed.
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Created attachment 12805
--> https://sourceware.org/bugzilla/attachment.cgi?id=12805&action=edit
patch to make test-case trigger internal-error
[ Looks like a duplicate of PR25067. ]
Using the attached patch on test-case gdb.base/eh_return.exp, we run into:
...
(gdb) break eh2:here^M
src/gdb/linespec.c:3233: internal-error: void decode_line_full(const
event_location*, int, program_space*, symtab*, int, linespec_result*, const
char*, const char*): Assertion `result.size () == 1 || canonical->pre_expanded'
failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
...
Also reproduces if we first run to eh2:
...
$ gdb \
outputs/gdb.base/eh_return/eh_return \
-batch \
-ex "b eh2" \
-ex run \
-ex "b here"
Breakpoint 1 at 0x4006af: file eh_return.c, line 52.
Breakpoint 1, eh2 (p=0x40071c <continuation>) at eh_return.c:52
52 eh2a (val, val, val, val, val, val, val, val, p);
linespec.c:3233: internal-error: void decode_line_full(const event_location*,
int, program_space*, symtab*, int, linespec_result*, const char*, const char*):
Assertion `result.size () == 1 || canonical->pre_expanded' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-27 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 7:26 vries at gcc dot gnu.org [this message]
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
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@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).