| Summary: | who_points_at should report the field in the object that does the pointing | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Noel Grandin <noelgrandin> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | minor | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Assuming we have debug information, it would be nice if the (gdb) monitor who_points_at 0xsomething command, could dig into the gdb typeinfo and report which field contains the pointer value. If that turns out to be too hard, a good second-option solution would be adding an extra option (gdb) monitor who_points_at 0xsomething print which (a) calculates the start address of the containing object (b) finds out the type of the containting object (valgrind seems to know this already) (c) calls (gdb) print *(T *)0xsourceobject which will make gdb print out the whole containing object. Thanks