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.
|Suggests:||covr, testthat, tibble|
|Author:||Kirill Müller [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>|
|CRAN checks:||procmaps results|
|Windows binaries:||r-devel: procmaps_0.0.4.zip, r-release: procmaps_0.0.4.zip, r-oldrel: procmaps_0.0.4.zip|
|macOS binaries:||r-release (arm64): procmaps_0.0.4.tgz, r-oldrel (arm64): procmaps_0.0.4.tgz, r-release (x86_64): procmaps_0.0.4.tgz, r-oldrel (x86_64): procmaps_0.0.4.tgz|
|Old sources:||procmaps archive|
Please use the canonical form https://CRAN.R-project.org/package=procmaps to link to this page.