Bug 16435 - Assertion `!value_lazy (var->value)' failed
Summary: Assertion `!value_lazy (var->value)' failed
Status: RESOLVED OBSOLETE
Alias: None
Product: gdb
Classification: Unclassified
Component: varobj (show other bugs)
Version: 7.6
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-11 13:01 UTC by Ákos Szőts
Modified: 2023-08-31 16:41 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
Project(s) to access:
ssh public key:

Attachments
C++ code which causes GDB to crash in line 18 (278 bytes, text/x-csrc)
2014-01-11 13:01 UTC, Ákos Szőts 		Details
Core dump of GDB (2.20 MB, application/x-xz)
2014-01-11 13:03 UTC, Ákos Szőts 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ákos Szőts 2014-01-11 13:01:44 UTC 
Created attachment 7349 [details]
C++ code which causes GDB to crash in line 18

I debug a C++ algorithm in Eclipse with GDB. With the attached code I can reliably reproduce the following GDB crash:

../../gdb/varobj.c:3548: internal-error: c_value_of_variable: Assertion `!value_lazy (var->value)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Versions:
OS: openSUSE 13.1
GDB: 7.6.50.20130731
GCC: 4.8.1
Comment 1 Ákos Szőts 2014-01-11 13:03:00 UTC 
Created attachment 7350 [details]
Core dump of GDB
Comment 2 Keith Seitz 2018-04-18 19:49:06 UTC 
I apologize this bug has gone without response for over four years. I saw the reclassification of this to varobj and decided to take a peek.

Unfortunately, without more information, it is not likely there is anything we can do. While I've tried to guess at what Eclipse was doing when the assertion happened, I have been unable to trigger this [using a 7.6 release].

So to start, is this still a problem with a recent release like 8.0 or 8.1?

If it is, could you please attach the output of Eclispe's logging? That would really help me reproduce the exact problem you are reporting.
Comment 3 Tom Tromey 2023-08-31 16:41:12 UTC 
I also wonder what commands were sent.
Anyway, going to close now due to lack of response.