HeapTrack Query - Stripped Binary

[sindhu krishnan]

Thank you For the inputs!

I'm using heaptrack version 1.2.0 and libunwind 1.3.1. I will try with
libunwind version 1.6.2.

Is there any way to provide debug symbols separately when using a stripped
binary?

I dont see any issue with heaptrack for simple "hello world" program and
for some applications with fewer dependencies. However, I have observed
crashes in applications that have multiple dependent libraries.

How do I execute heaptrack for a running process? Do I only need to attach
the process to heaptrack, or can I modify the service file to start the
process directly with heaptrack?

Thanks for your help


On Tue, Jun 13, 2023, 3:58 PM Milian Wolff <mail at milianw.de> wrote:

> On Dienstag, 13. Juni 2023 11:20:53 CEST sindhu krishnan wrote:
> > Attaching the backtrace of the crash:
> >
> > Program terminated with signal SIGSEGV, Segmentation fault.
> > #0  0xb3466b3e in _ULarm_step () from /usr/lib/libunwind.so.8
> > [Current thread is 1 (LWP 30383)]
> > (gdb) bt
> > #0  0xb3466b3e in _ULarm_step () from /usr/lib/libunwind.so.8
> > #1  0xb3466110 in unw_backtrace () from /usr/lib/libunwind.so.8
> > #2  0xb3f68f32 in heaptrack_malloc () from
> > /usr/lib/heaptrack/libheaptrack_preload.so
> > #3  0xb3f67582 in posix_memalign () from
> > /usr/lib/heaptrack/libheaptrack_preload.so
> > #4  0xb393b1d2 in ?? () from /usr/lib/libglib-2.0.so.0
> > Backtrace stopped: previous frame identical to this frame (corrupt
> stack?)
> > (gdb)
>
> What version of heaptrack and libunwind are you using? What UNW_ARM_METHOD
> are
> you using?
>
> Note how this crashes within libunwind, not in heaptrack so in the end
> this
> isn't something I can help you with really except saying you need to use a
> recent libunwind and that `UNW_ARM_METHOD=4` might be more resilient.
>
> Good luck
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/heaptrack/attachments/20230615/4171b2dd/attachment.htm>