Bug 397474 - Heaptrack crashes while starting the binary
Summary: Heaptrack crashes while starting the binary
Status: RESOLVED WORKSFORME
Alias: None
Product: Heaptrack
Classification: Applications
Component: general (show other bugs)
Version: 1.1.0
Platform: Debian unstable Linux
: NOR grave
Target Milestone: ---
Assignee: Milian Wolff
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-08-15 08:32 UTC by Damian Szuberski
Modified: 2018-10-29 02:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Damian Szuberski 2018-08-15 08:32:10 UTC
Debian unstable, heaptrack (1.1.0-3). 

heaptrack output will be written to "(CENSORED)/heaptrack.BTSOMexe.21695.gz"
starting application, this might take some time...
heaptrack_interpret: /build/heaptrack-diwsCt/heaptrack-1.1.0/src/util/linewriter.h:84: bool LineWriter::write(const char*, T ...) [with T = {const char*}]: Assertion `false && "message doesn't fit into buffer"' failed.

Debian testing, heaptrack (1.0.1~20180129.gita4534d5-1) works perfectly well and the bug above doesn't show.
Comment 1 Milian Wolff 2018-08-15 08:42:29 UTC
I'll need a way to reproduce this, as I otherwise cannot help with fixing this bug. Otherwise, you'll have to debug this yourself and figure out why the message constructed becomes larger than what fits into the buffer.

Also, try to build the latest git master and see if that helps.
Comment 2 Damian Szuberski 2018-08-16 06:35:44 UTC
Thank you for fast reaction.

Unfortunately the binary tested under heaptrack was a proprietary one. I'll try the bleeding edge master and at the same time try to prepare a simple reproduction.
Comment 3 Christoph Feck 2018-09-05 00:00:46 UTC
Damian, any success with comment #1?
Comment 4 Andrew Crouthamel 2018-09-28 03:33:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:19:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!