Re: overflows in Dwfl_Thread_Callbacks::memory_read callback

2017-06-14 Thread Mark Wielaard
On Tue, 2017-06-13 at 18:15 +0200, Milian Wolff wrote: > > I am not following the above trace completely, but what is going on > > seems to be that we have CFI and want to get a register value. So we > > call dwarf_frame_register to determine the DWARF expression operations > > that we need to exec

Re: overflows in Dwfl_Thread_Callbacks::memory_read callback

2017-06-13 Thread Milian Wolff
On Dienstag, 13. Juni 2017 16:06:01 CEST Mark Wielaard wrote: > On Thu, 2017-06-01 at 22:46 +0200, Milian Wolff wrote: > > in the perfparser that Ulf wrote, and to which I'm contributing too, we > > often see abnormal data being passed to the memory_read callback we > > define. > > > > I.e. our ca

Re: overflows in Dwfl_Thread_Callbacks::memory_read callback

2017-06-13 Thread Mark Wielaard
On Thu, 2017-06-01 at 22:46 +0200, Milian Wolff wrote: > in the perfparser that Ulf wrote, and to which I'm contributing too, we often > see abnormal data being passed to the memory_read callback we define. > > I.e. our callback gets invoked with addr=0x which clearly > isn't an