Bug 17076 - SIGSEGV in value_entirely_optimized_out when printing c++ objects
Summary: SIGSEGV in value_entirely_optimized_out when printing c++ objects
Status: RESOLVED DUPLICATE of bug 20020
Alias: None
Product: gdb
Classification: Unclassified
Component: exp (show other bugs)
Version: 7.7
: P2 normal
Target Milestone: 8.3.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-20 00:18 UTC by Luc des Trois Maisons
Modified: 2024-06-30 17:48 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Stack trace for SIGSEGV (1.14 KB, text/plain)
2014-06-20 00:18 UTC, Luc des Trois Maisons 		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 Luc des Trois Maisons 2014-06-20 00:18:52 UTC 
Created attachment 7650 [details]
Stack trace for SIGSEGV

I'm using 7.7.1.  When I attempt to print the fields of objects in a core file I've generated, GDB will crash with the attached trace.

I've attempted this on various objects in this core file.  It seems that often manages a partial output before going off the deep end.
Comment 1 Tom Tromey 2023-03-29 14:16:21 UTC 
We'd probably need a test program, assuming this wasn't fixed
in the intervening 9 years.
Anyway, switching components, this probably isn't related to core files.
Comment 2 Hannes Domani 2024-06-30 17:48:28 UTC 
Dup.

*** This bug has been marked as a duplicate of bug 20020 ***