Any way, re-reading your post yes, the info is in there. If the address is known, GDB can pull the contents out of memory. Given the list of targets:
- core
- native attach
- native run
- remote
- ?more?
I believe the choices are:
- find a way of determing that address across all of these targets :-/
- implement per-target custom mechanisms for pulling out this information (creating a need to test/implement each target separatly - vis the corefile + dwarf2 changes) :-//
So, it possible to find the address (symbol?, /proc, shlib load table, ...?) for all targets?
/proc/PID/map, on a remote, is a possability. A remote version of find_memory_regions() would be useful anyway - clean up gcore a bit. However, the down side is that a system with no /proc mounted wouldn't debug very well :-/