{"id":608600,"date":"2023-02-16T07:48:57","date_gmt":"2023-02-16T13:48:57","guid":{"rendered":"https:\/\/news.sellorbuyhomefast.com\/index.php\/2023\/02\/16\/show-hn-i-wrote-a-tool-in-rust-for-tracking-all-allocations-in-a-linux-process\/"},"modified":"2023-02-16T07:48:57","modified_gmt":"2023-02-16T13:48:57","slug":"show-hn-i-wrote-a-tool-in-rust-for-tracking-all-allocations-in-a-linux-process","status":"publish","type":"post","link":"https:\/\/newsycanuse.com\/index.php\/2023\/02\/16\/show-hn-i-wrote-a-tool-in-rust-for-tracking-all-allocations-in-a-linux-process\/","title":{"rendered":"Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process"},"content":{"rendered":"
\n
\n

\"allocscope<\/a><\/p>\n

allocscope<\/h2>\n

a memory tracking tool<\/h3>\n

allocscope is a tool for tracking down where the most egregiously large allocations are occurring
\nin a C, C++ or Rust codebase. It is particilarly intendend to be useful for developers who want to
\nget a handle on excessive allocations and are working in a large codebase with multiple
\ncontributors with allocations occuring in many modules or libraries.<\/p>\n

It is composed of two commands:<\/p>\n

allocscope-trace<\/code> attaches to another process as a debugger. By using breakpoints on memory
\nallocation functions such as malloc<\/code> it tracks allocations made by that process. During the
\ntrace, the callstack of all allocations are recorded to an .atrace<\/code> file. Tracing programs
\nwhich spawn multiple threads and tracing calls through shared libraries are supported. You can
\nspawn a process to trace by specifying a full commandline to allocscope-trace<\/code>, or you can
\nattach to an existing running process.<\/p>\n

allocscope-view<\/code> reads the .atrace<\/code> file produced by allocscope-trace<\/code>. It presents a summary
\nof all allocations made in a call tree format, which can be sorted by largest concurrent
\nallocation, total number of blocks, number of unfreed allocation blocks, or the sequence of
\nthe allocation. The summary can be navigated interactively through a curses-based terminal user
\ninterface, or a text report suitable for non-interactive use can be generated.<\/p>\n

Installing prebuilt binaries<\/h2>\n

The easiest way to get started with allocscope is to install prebuilt binaries.<\/p>\n

To install the latest version:<\/p>\n

curl -s https:\/\/allocscope.com\/install.sh | sudo sh<\/code><\/p>\n

Currently only Linux on x86_64 processors is supported, but I’d like to support more operating systems
\nand processors in the future.<\/p>\n

Getting started<\/h2>\n

While it will be likely be most useful to use allocscope on a program with symbols, which you
\nhave compiled yourself, you can verify that it functions correctly by performing a trace on a
\nstandard system command, such as ls<\/code>:<\/p>\n

<\/p>\n
allocscope-trace ls -l\nallocscope-view ls.atrace\n<\/code><\/pre>\n<\/div>\n
Building from source<\/h2>\n
On recent Ubuntu releases, allocscope can be built from source with the following sequence
\nof commands:<\/p>\n
<\/p>\n
apt-get update\napt-get install cargo git libclang-dev libiberty-dev libncurses-dev libsqlite3-dev libunwind-dev\ngit clone https:\/\/github.com\/matt-kimball\/allocscope.git\ncd allocscope\ncargo install --path allocscope-trace\ncargo install --path allocscope-view\n<\/code><\/pre>\n<\/div>\n
Statically linked binaries can also be built using the build-static\/build.sh<\/code> script, though this requires
\nDocker installed on the build system.<\/p>\n
Support development<\/h2>\n
If you find allocscope useful, please consider supporting development.<\/p>\n
Visit https:\/\/allocscope.com\/support<\/a><\/p>\n
License<\/h2>\n
allocscope is licensed GNU General Public License version 3.<\/p>\n<\/p><\/div>\n
Read More<\/a>
\n Tama Pingree<\/p>\n","protected":false},"excerpt":{"rendered":"
allocscope a memory tracking tool allocscope is a tool for tracking down where the most egregiously large allocations are occurring in a C, C++ or Rust codebase. It is particilarly intendend to be useful for developers who want to get a handle on excessive allocations and are working in a large codebase with multiple contributors<\/p>\n","protected":false},"author":1,"featured_media":608601,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[46,2034,4689],"tags":[],"class_list":{"0":"post-608600","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"category-tracking","9":"category-wrote"},"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/posts\/608600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/comments?post=608600"}],"version-history":[{"count":0,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/posts\/608600\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/media\/608601"}],"wp:attachment":[{"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/media?parent=608600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/categories?post=608600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsycanuse.com\/index.php\/wp-json\/wp\/v2\/tags?post=608600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}