https://bugs.kde.org/show_bug.cgi?id=512667
Bug ID: 512667
Summary: heaptrack not able to generate stack trace on yocto
build environment
Classification: Applications
Product: Heaptrack
Version First 1.5.0
Reported In:
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Unable to get stack trace from heaptrack application when launched on embedded
target with Yocto version 5.0.
heaptrack is able to run and launch the Application but generated data files
are very small in size. When checked using host based heaptrack tool, stack is
almost empty only.
STEPS TO REPRODUCE
1. Compile heaptrack application v1.5.0 for yocto v5 varaint
2. Add heaptrack application entry for package config so that all the
dependent libs gets installed to target path
3. launch the application using "heaptrack /usr/bin/<application_nam>"
After end of application exit,
heaptrack stats:
allocations: 18711
leaked allocations: 557
temporary allocations: 190
Heaptrack finished! Now run the following to investigate the data:
heaptrack --analyze
"/data/heaptrack/heaptrack.location_client_api_testapp.2777.gz"
/data/heaptrack #
/data/heaptrack # ls -lt
total 976
-rwxrwxrwx 1 root root 626560 Nov 21 09:19
location_client_api_testapp
-rw-rw-rw- 1 root root 8719 Nov 21 09:20
heaptrack.location_client_api_testapp.2995.gz
-rw-rw-rw- 1 root root 9209 Nov 21 08:59
heaptrack.location_client_api_testapp.2963.gz
-rw-rw-rw- 1 root root 6974 Nov 13 05:35
heaptrack.location_client_api_testapp.2878.gz
-rw-rw-rw- 1 root root 8842 Nov 14 10:03
heaptrack.location_client_api_testapp.2863.gz
-rw-rw-rw- 1 root root 8922 Nov 21 06:02
heaptrack.location_client_api_testapp.2850.gz
-rw-rw-rw- 1 root root 24540 Nov 13 05:32
heaptrack.location_client_api_testapp.2837.gz
-rw-rw-rw- 1 root root 71829 Nov 13 10:08
heaptrack.location_client_api_testapp.2828.gz
-rw-rw-rw- 1 root root 19135 Nov 21 05:46
heaptrack.location_client_api_testapp.2815.gz
-rw-rw-rw- 1 root root 13551 Nov 21 05:42
heaptrack.location_client_api_testapp.2777.gz
OBSERVED RESULT
Observed below result when try to decode the data generated from taget path.
heaptrack_print heaptrack.location_client_api_testapp.2777.gz
reading file "heaptrack.location_client_api_testapp.2777.gz" - please wait,
this might take some time...
Debuggee command was: /usr/bin/location_client_api_testapp
finished reading file, now analyzing data:
MOST CALLS TO ALLOCATION FUNCTIONS
33292 calls to allocation functions with 481.23K peak consumption from
0x0
in ??
PEAK MEMORY CONSUMERS
481.23K peak memory consumed over 33292 calls from
0x0
in ??
MOST TEMPORARY ALLOCATIONS
312 temporary allocations of 33292 allocations in total (0.94%) from
0x0
in ??
total runtime: 22.03s.
calls to allocation functions: 33292 (1511/s)
temporary memory allocations: 312 (14/s)
peak heap memory consumption: 481.23K
peak RSS (including heaptrack overhead): 10.27M
total memory leaked: 307.52K
EXPECTED RESULT
heaptrack output with proper stack trace
SOFTWARE/OS VERSIONS
Linux: Ubuntu 22.0, Host heaptrack version "$ heaptrack --version
heaptrack 1.3.0
"
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
