[3pt] Demangling of C symbols inside memprof
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Since: 2.10
Root document: https://www.tarantool.io/en/doc/latest/book/app_server/luajit_memprof/
Dev issue: https://github.com/tarantool/tarantool/issues/5813
SME: @ igormunkin , @ Buristan
Details
We can use the Dl_info and dladdr() functions to provide the name of the <*.so> file and the name of the C function, where the allocation event occurred. It's better than just a raw C address that shows nothing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the root document at book/app_server/luajit_memprof/ and read the linked development issue #5813. Check how memprof currently reports allocation addresses and define done as reporting the shared-object and C function names instead of only a raw C address, using Dl_info and dladdr() as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- devtools, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100