procmaps: Portable Address Space Mapping

Portable '/proc/self/maps' as a data frame. Determine which library or other region is mapped to a specific address of a process. – R packages can contain native code, compiled to shared libraries at build or installation time. When loaded, each shared library occupies a portion of the address space of the main process. When only a machine instruction pointer is available (e.g. from a backtrace during error inspection or profiling), the address space map determines which library this instruction pointer corresponds to.

Version: 0.0.5
Suggests: covr, testthat, tibble
Published: 2023-01-20
DOI: 10.32614/CRAN.package.procmaps
Author: Kirill Müller ORCID iD [aut, cre], R Consortium [fnd], Kostya Serebryany [ctb] (Bundled gperftools library), Sanjay Ghemawat [ctb] (Bundled gperftools library), Craig Silverstein [ctb] (Bundled gperftools library), Google Inc. [cph] (Bundled gperftools library)
Maintainer: Kirill Müller <kirill at>
License: GPL-3
NeedsCompilation: yes
Materials: README NEWS
CRAN checks: procmaps results


Reference manual: procmaps.pdf


Package source: procmaps_0.0.5.tar.gz
Windows binaries: r-devel:, r-release:, r-oldrel:
macOS binaries: r-release (arm64): procmaps_0.0.5.tgz, r-oldrel (arm64): procmaps_0.0.5.tgz, r-release (x86_64): procmaps_0.0.5.tgz, r-oldrel (x86_64): procmaps_0.0.5.tgz
Old sources: procmaps archive

Reverse dependencies:

Reverse imports: winch


Please use the canonical form to link to this page.