https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
thanks for the report, I can't give you any ETA on when I have the time to look
into this as I'm pretty swamped in the current situation.
could you maybe try to inspect it yourself? Basically you'd have to build
heaptrack from source yourself and then enable logging - that would be my first
step too. Maybe we can see something fishy by looking at the log then.
basically all you need to do is checkout current master, create a build dir,
run `cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo path/to/sources && cmake --build
.`, then see if you can run it:
```
./bin/heaptrack ./tests/manual/test_c
heaptrack output will be written to
"/home/milian/projects/build/heaptrack/heaptrack.test_c.25458.zst"
starting application, this might take some time...
malloc: 0x5614afb04160
heaptrack stats:
allocations: 3
leaked allocations: 0
temporary allocations: 0
Heaptrack finished! Now run the following to investigate the data:
heaptrack --analyze
"/home/milian/projects/build/heaptrack/heaptrack.test_c.25458.zst"
```
then enable logging by editing path/to/heaptrack/src/track/libheaptrack.cpp and
change
constexpr const DebugVerbosity s_debugVerbosity = NoDebugOutput;
to
constexpr const DebugVerbosity s_debugVerbosity = VeryVerboseOutput;
recompile, then run on rustc and pipe the full output into a log file. then
attach the compressed log file here please
thanks
--
You are receiving this mail because:
You are watching all bug changes.
