public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nrw at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type
Date: Thu, 18 Nov 2021 13:04:11 +0000 [thread overview]
Message-ID: <bug-28605-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
Bug ID: 28605
Summary: internal-error: Should not be able to create a lazy
value with an enclosing type
Product: gdb
Version: 11.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: nrw at yandex dot ru
Target Milestone: ---
Crash in gdb/dwarf2/loc.c:1730: internal-error: Should not be able to create a
lazy value with an enclosing type
It's happens randomly during debug under QtCreator Linux Mangaro XFCE.
Full text from QtCreator debugger log:
>&"python theDumper.fetchVariables({\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":300,\"dyntype\":1,\"expanded\":[\"watch\",\"return\",\"local\",\"inspect\"],\"fancy\":1,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"\",\"passexceptions\":0,\"qobjectnames\":1,\"resultvarname\":\"\",\"stringcutoff\":10000,\"timestamps\":0,\"token\":37,\"typeformats\":{},\"watchers\":[]})\n"
>~"../../gdb/dwarf2/loc.c:1730: internal-error: Should not be able to create a lazy value with an enclosing type\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable."
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-11-18 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 13:04 nrw at yandex dot ru [this message]
2021-11-25 7:52 ` [Bug c++/28605] " nrw at yandex dot ru
2022-02-19 16:40 ` tromey at sourceware dot org
2022-04-02 16:44 ` tromey at sourceware dot org
2022-10-21 17:05 ` tromey at sourceware dot org
2023-01-30 23:24 ` 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-28605-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).