Opened 13 years ago

Last modified 9 years ago

#7839 new bug

entry_refs inside BMessages aren't quite handled correctly

Reported by: anevilyak Owned by: anevilyak
Priority: low Milestone: Unscheduled
Component: Applications/Debugger Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Making a ticket so this isn't forgotten. Currently, when the BMessageValueNode encounters an entry_ref field, it maps that to be handled by the corresponding DWARF type for the actual entry_ref structure. However, this isn't entirely correct since the flat format differs slightly from the in-memory format (the latter has the name field as a pointer to an allocated string, whereas the former packs an array directly into the structure). Consequently the name field isn't displayed properly. This needs to be fixed by adding debug_info support for creating/registering synthetic types.

Change History (1)

comment:1 by luroh, 9 years ago

Milestone: R1Unscheduled

Moving Debugger related tickets out of R1 milestone (Prop #14).

Note: See TracTickets for help on using tickets.