[Bug gdb/28681] Wrong pretty-printed unique_ptr value when using "finish"

["simark at simark dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28681

--- Comment #6 from Simon Marchi <simark at simark dot ca> ---
> And it is when we ask for the loc_bitpos that the assert triggers, as the
> field's type is no FIELD_LOC_KIND_BITPOS, but is instead,
> FIELD_LOC_KIND_DWARF_BLOCK.
> 
> In the case we're handling, the field being processed is the field that
> describes the virtual base of the type being processed.
> 
> I originally starting playing with is_dynamic_type, but noticed that the
> type in question doesn't return true for is_dynamic_type.  This seemed
> weird, as clearly the offset needs resolving.  But then I found some code in
> is_dynamic_type_internal which specifically detects the exact case I'm
> looking at, and ensures that such a case is NOT enough to make a type appear
> dynamic.  The comment on this code says:
> 
> 	    /* Do not consider C++ virtual base types to be dynamic
> 	       due to the field's offset being dynamic; these are
> 	       handled via other means.  */
> 
> But, frustratingly, doesn't indicate what that other means is, or where I
> might find it.

Ok, it is that issue I was curious about.  It sounds similar to this, but at a
different place:

https://sourceware.org/pipermail/gdb-patches/2021-September/182307.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.