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.3
Suggests: covr, testthat, tibble
Published: 2020-09-22
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 <krlmlr+r at mailbox.org>
BugReports: https://github.com/r-prof/procmaps/issues
License: GPL-3
URL: https://r-prof.github.io/procmaps/, https://github.com/r-prof/procmaps
NeedsCompilation: yes
Materials: README NEWS
CRAN checks: procmaps results

Downloads:

Reference manual: procmaps.pdf
Package source: procmaps_0.0.3.tar.gz
Windows binaries: r-devel: procmaps_0.0.3.zip, r-release: procmaps_0.0.3.zip, r-oldrel: procmaps_0.0.3.zip
macOS binaries: r-release: procmaps_0.0.3.tgz, r-oldrel: procmaps_0.0.3.tgz
Old sources: procmaps archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=procmaps to link to this page.