Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Java HPROF memory dump parser written in Rust

NotificationsYou must be signed in to change notification settings

monoid/hprof_dump_parser

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

43 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OpenJDK HPROF dump parsing library.Based onhttps://hg.openjdk.java.net/jdk/jdk/file/9a73a4e4011f/src/hotspot/share/services/heapDumper.cppandhttp://hg.openjdk.java.net/jdk6/jdk6/jdk/raw-file/tip/src/share/demo/jvmti/hprof/manual.htmlCurrently, the supported ID sizes (actually, pointer sizes) are 4 and 8.The library provides a streaming interface (iterator over dumprecords).  Class structure information and string dictionary are keptin memory as they are required for unpacking object data.There are two modes of operation: reading from std::io::BufRead withStreamHprofReader::read_hprof_from_stream (strings arereturned as Vec<u8>) and from memory withStreamHprofReader::read_hprof_from_memory (strings are returned as&'memory [u8], where 'memory is memory lifetime).Values stored in Record::String (i.e. strings by themselves) do not alwayshave valid UTF-8 data, that's why they are returned as byte vectors/slices.Strings are returned as Record::String(id, data), andfrom object dump, these strings are refered by their id; thiscrate doesn't resolve these ids into strings (and objects are notresolved either), you have to keep id->data mapping by yourself.Author: Ivan Boldyrev <lispnik@gmail.com>

About

Java HPROF memory dump parser written in Rust

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published

[8]ページ先頭

©2009-2025 Movatter.jp