jetchirag

Thank you for testing @CptGibbon Currently only `jemalloc_heap`,`jemalloc_find_extent`and `jemalloc_extent_info` are to be used, rest are just for testing purpose. Since I've changed the structure a lot, some old test ones...

> So far my only concern aside from the address issue is that jemalloc_heap was rather slow to complete, at around 3 seconds. This was running on a free codespaces...

@CptGibbon I'll check that function. I don't think there's much code taken directly from that script. The code for bit shifting bitfield was directly used https://github.com/pwndbg/pwndbg/pull/2176/files#diff-c96fafbf3d980a07d7f741d99185b64e1a09dd7371ac617dc6f7bffb25b7f68bR380-R389 and `rtree_leaf_elm_bits_extent_get` Primarily I...

> One last note; if you want your test program to get linked with jemalloc you'll need to add a corresponding line to the makefile that builds tests. Is it...

I noticed the duplicate flag in makefile, will remove that

I looked at cache stores in thread specific information structure and elsewhere but we won't be able to use it for finding extents. I think I will have to stick...

Can you please also answer if these commands (just the functionality) fulfil the primary scope of this project?

@CptGibbon mypy is not sure about the type of sub dicts in GdbDict from that struct as dictionary function and thus there are several error messages in linting. Is there...

@disconnect3d @CptGibbon I've added more comments describing most of the code and jemalloc itself.

I'm using vscode remote development on a VPS. - pwndbg - [jemalloc](https://github.com/jemalloc/jemalloc/blob/dev/INSTALL.md) (5.3.0) run.sh ``` cd "$(dirname "$0")" filename=test rm -f $filename gcc -g -O0 $filename.cpp -o $filename `jemalloc-config --libdir`/libjemalloc.a...