public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type
@ 2021-11-18 13:04 nrw at yandex dot ru
2021-11-25 7:52 ` [Bug c++/28605] " nrw at yandex dot ru
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: nrw at yandex dot ru @ 2021-11-18 13:04 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/28605] internal-error: Should not be able to create a lazy value with an enclosing type
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
@ 2021-11-25 7:52 ` nrw at yandex dot ru
2022-02-19 16:40 ` tromey at sourceware dot org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: nrw at yandex dot ru @ 2021-11-25 7:52 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
--- Comment #1 from Roman Nikulenkov <nrw at yandex dot ru> ---
on the same code version 10.2 works without any issues
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/28605] internal-error: Should not be able to create a lazy value with an enclosing type
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
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
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: tromey at sourceware dot org @ 2022-02-19 16:40 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I think we'd need more information to try to fix this bug.
One thing that might be useful is a stack trace showing
the path taken by gdb to the error.
The very best thing would be a small C++ test case and a sequence
of commands that can be used to reproduce the crash. (I realize
this is probably hard though)
I somewhat suspect that the assertion is in error, as the code
says:
if (from != nullptr)
{
from_contents = value_contents (from).data ();
v_contents = nullptr;
}
else
{
if (value_type (v) != value_enclosing_type (v))
internal_error (__FILE__, __LINE__,
_("Should not be able to create a lazy value with "
"an enclosing type"));
... but when I look at this I don't see anything that's obviously
checking for a lazy value.
However, looking at the most recent patch in this area, I see the
assertion goes back a ways. So I'm not certain that the check
is wrong, and I wonder what really changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/28605] internal-error: Should not be able to create a lazy value with an enclosing type
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
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
4 siblings, 0 replies; 6+ messages in thread
From: tromey at sourceware dot org @ 2022-04-02 16:44 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-04-02
Status|UNCONFIRMED |WAITING
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/28605] internal-error: Should not be able to create a lazy value with an enclosing type
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
` (2 preceding siblings ...)
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
4 siblings, 0 replies; 6+ messages in thread
From: tromey at sourceware dot org @ 2022-10-21 17:05 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
See https://sourceware.org/pipermail/gdb-patches/2022-October/192547.html
There are other threads in earlier months as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/28605] internal-error: Should not be able to create a lazy value with an enclosing type
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
` (3 preceding siblings ...)
2022-10-21 17:05 ` tromey at sourceware dot org
@ 2023-01-30 23:24 ` tromey at sourceware dot org
4 siblings, 0 replies; 6+ messages in thread
From: tromey at sourceware dot org @ 2023-01-30 23:24 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=28605
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
That patch landed but I tend to think we should clear the
enclosing type when modifying a value's type.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-01-30 23:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-18 13:04 [Bug c++/28605] New: internal-error: Should not be able to create a lazy value with an enclosing type nrw at yandex dot ru
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
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).