Re: [Libunwind-devel] Crash in access_mem at x86_64/Ginit.c:175

[Dave Watson]

On 02/23/18 10:30 AM, Jérémy Coulon wrote:
> Hello!
> 
> I am having a crash in libunwind while using heaptrack to profile my
> application.
> 
> Here is the callstack:
> 
> Thread 56 (Thread 0x7ffeff661700 (LWP 5926)):
> #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 (address@hidden) 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 x86_64/Gtrace.c:330
> 
> I am using:
> * heaptrack version v1.0.0-119-g6e31841
> * libunwind version v1.2-3-gac02808
> 

There were several recent fixes to access_mem since v1.2, including 
https://github.com/libunwind/libunwind/commit/05d814b64036b1ea2f0f328b3a985b03559dcf10
https://github.com/libunwind/libunwind/commit/836c91c43d7a996028aa7e8d1f53630a6b8e7cbe

Can you try master and see if any of those patches fix your issue?

Thanks