diff options
| author | John Baldwin <jhb@FreeBSD.org> | 2015-02-17 19:15:45 -0500 |
|---|---|---|
| committer | John Baldwin <jhb@FreeBSD.org> | 2015-03-13 14:08:15 -0400 |
| commit | 25268153a182eef28d31ed2bc03ab7c6c0ab40e3 (patch) | |
| tree | c50a9b2391d7d6eb223ec9c49bc4920615b3b4a6 /gdb/c-varobj.c | |
| parent | 773eacf5b0362c755ac47cb66d15d07558d9ce20 (diff) | |
| download | gdb-25268153a182eef28d31ed2bc03ab7c6c0ab40e3.zip gdb-25268153a182eef28d31ed2bc03ab7c6c0ab40e3.tar.gz gdb-25268153a182eef28d31ed2bc03ab7c6c0ab40e3.tar.bz2 | |
Use kinfo_getvmmap on FreeBSD to enumerate memory regions.
Use kinfo_getvmmap from libutil on FreeBSD to enumerate memory
regions in a running process instead of /proc/<pid>/map. FreeBSD systems
do not mount procfs by default, but kinfo_getvmmap uses a sysctl that
is always available.
Skip memory regions for devices as well as regions an application has
requested to not be dumped via the MAP_NOCORE flag to mmap or
MADV_NOCORE advice to madvise.
gdb/ChangeLog:
* configure.ac: AC_CHECK_LIB(util, kinfo_getvmmap).
* configure: Regenerate.
* config.in: Regenerate.
* fbsd-nat.c [!HAVE_KINFO_GETVMMAP] (fbsd_read_mapping): Don't
define.
(fbsd_find_memory_regions): Use kinfo_getvmmap to
enumerate memory regions if present.
Diffstat (limited to 'gdb/c-varobj.c')
0 files changed, 0 insertions, 0 deletions