Heaptrack crashes with an Aarch64 based Poky/Yocto Linux: /usr/lib/heaptrack/libheaptrack_preload.so starting application, this might take some time... dbus[17204]: arguments to dbus_set_error_from_message() were incorrect, assertion "(error) == NULL || !dbus_error_is_set ((error))" failed in file ../../dbus-1.12.20/dbus/dbus-message.c line 4077. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace /usr/bin/heaptrack: line 349: 17204 Aborted (core dumped) LD_PRELOAD="$LIBHEAPTRACK_PRELOAD${LD_PRELOAD:+:$LD_PRELOAD}"
Which application are you trying to run, can I try this too? Heaptrack doesn't use dbus internally, so this information here alone isn't enough. I've used heaptrack just fine on aarch64/yocto systems in the past.
I have a theory, so I'll start with a question: Does heaptrack change anything about the memory layout of the application like GDB does (think ASLR)? Or in other words, can heaptrack change the memory layout of the application in a way that a library that has problems with uninitialized memory could crash when it didn't before?
if you have problems with uninit memory then you are in UB land and everything can happen. So by definition the answer to your question is: yes. We don't do any specific ASLR related stuff though. You can try to run `heaptrack -d` which will then drop into a GDB shell after setting up heaptrack for your application. That way you can get a full backtrace when the crash occurs, if it points at heaptrack I'm interested, otherwise this sounds unrelated to what heaptrack itself is doing.
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 mark the bug 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!
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!