The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
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 [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 cynkra.com> |
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 |
Reference manual: | procmaps.pdf |
Package source: | procmaps_0.0.5.tar.gz |
Windows binaries: | r-devel: procmaps_0.0.5.zip, r-release: procmaps_0.0.5.zip, r-oldrel: procmaps_0.0.5.zip |
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 imports: | winch |
Please use the canonical form https://CRAN.R-project.org/package=procmaps to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.