[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 --- Comment #6 from jeremy.coulon.j...@gmail.com --- Well I think using heaptrack for a pure Java application wouldn't be helpful. However my application is a mix of Java and C++ with JNI. I already successfully profiled some smaller scenarii with

[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 Milian Wolff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 --- Comment #4 from jeremy.coulon.j...@gmail.com --- Gdb was executed on: * heaptrack version v1.0.0-119-g6e31841 * libunwind version v1.2-3-gac02808 -- You are receiving this mail because: You are watching all bug changes.

[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 --- Comment #3 from jeremy.coulon.j...@gmail.com --- I attached the result of 'thread apply all bt'. I have 70 threads and multiple threads are doing malloc/free at the same time. The problematic thread is thread 56. -- You are receiving this mail

[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 --- Comment #2 from jeremy.coulon.j...@gmail.com --- Created attachment 110902 --> https://bugs.kde.org/attachment.cgi?id=110902=edit thread apply all bt -- You are receiving this mail because: You are watching all bug changes.

[Heaptrack] [Bug 390893] Crash while profiling my app

https://bugs.kde.org/show_bug.cgi?id=390893 --- Comment #1 from Milian Wolff --- try the following: heaptrack -d this should start your app in GDB and then preload heaptrack and run it like normally. Once you get the crash, get the output from `thread apply all bt` and paste