Milian Wolff <> changed:

           What    |Removed                     |Added
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |UPSTREAM

--- Comment #5 from Milian Wolff <> ---
A java application - interesting, never used heaptrack on that. The crash
itself happens within libunwind:

Thread 56 (Thread 0x7ffeff661700 (LWP 5926)):
#0  0x00007ffff71d9428 in __GI_raise (sig=sig@entry=6) at
#1  0x00007ffff71db02a in __GI_abort () at abort.c:89
#2  0x00007ffff55eeed5 in os::abort(bool) () from
#3  0x00007ffff5792a33 in VMError::report_and_die() () from
#4  0x00007ffff55f4def in JVM_handle_linux_signal () from
#5  0x00007ffff55eaea3 in signalHandler(int, siginfo*, void*) () from
#6  0x0000xxxxxxxxxxxx in handleCustom (sc_=<optimized out>, si=<optimized
out>, code=11, handlerCode=11) at ??
#7  mySignalHandler (code=11, si=<optimized out>, sc_=<optimized out>) at ??
#8  <signal handler called>
#9  access_mem (as=<optimized out>, addr=29930553589, val=0x7ffeff65eb90,
write=<optimized out>, arg=<optimized out>) at x86_64/Ginit.c:175
#10 0x00007ffff6f8829c in dwarf_get (c=0x7ffeff65f090, c=0x7ffeff65f090,
val=0x7ffeff65eb90, loc=...) at ../include/tdep-x86_64/libunwind_i.h:167
#11 _ULx86_64_step (cursor=cursor@entry=0x7ffeff65f090) at x86_64/Gstep.c:166
#12 0x00007ffff6f8942c in trace_init_addr (rsp=<optimized out>, rbp=<optimized
out>, rip=<optimized out>, cfa=31901497176, cursor=0x7ffeff65f090,
f=0x7fff4bfdc940) at x86_64/Gtrace.c:248
#13 trace_lookup (rsp=<optimized out>, rbp=<optimized out>, rip=<optimized
out>, cfa=31901497176, cache=<optimized out>, cursor=0x7ffeff65f090) at
#14 _ULx86_64_tdep_trace (cursor=cursor@entry=0x7ffeff65f090,
buffer=buffer@entry=0x7ffeff65f928, size=size@entry=0x7ffeff65ecd4) at
#15 0x00007ffff6f85db2 in unw_backtrace (buffer=0x7ffeff65f928, size=64) at
#16 0x00007ffff7bc19e0 in Trace::fill (this=0x7ffeff65f920, skip=3) at
#17 0x00007ffff7bbfbd0 in heaptrack_malloc (ptr=0x7ffec406b160, size=8) at
#18 0x00007ffff7bbd9dd in malloc (size=8) at
#19 0x00007ffff6c8ee78 in operator new(unsigned long) () from
#20 0x00007fff3a40f08e in __gnu_cxx::new_allocator<unsigned long>::allocate
(this=<optimized out>, __n=<optimized out>) at
#21 0x0000xxxxxxxxxxxx in ?? ()

Probably it tries to access invalid memory, triggering a signal which then
leads to the crash. To fix this, you'll have to fix libunwind, which is going
to be tough. First, you'll need to figure out whom to blame - is it a bug in
libunwind? Or is the DWARF data corrupt, misleading it? Can the latter be
handled somehow?

One way or another, this isn't a bug within heaptrack itself. It definitely
makes the tool unusable for you, but it's nothing that can be workarounded from
within heaptrack - it has to be fixed upstream (either libunwind or in the
DWARF emitter).

You are receiving this mail because:
You are watching all bug changes.

Reply via email to