On 1/15/2015 10:34 AM, Corinna Vinschen wrote:
Hi Marco,
On Jan 14 23:30, Marco Atzeri wrote:
Debugging a program I am trying to catch where this call is happening
17 1499678 [main] ncview 1484 free: (0x6000D7961), called by 0x180115A0B
unfortunately the 0x180115A0B address is not real caller
Hi Marco,
On Jan 16 15:23, Marco Atzeri wrote:
> On 1/15/2015 10:34 AM, Corinna Vinschen wrote:
> >Bottom line, you should be able to fetch the original return address by
> >printing the value at
> >
> > *(void*)_my_tls->stackptr
> >
> >which points to the uppermost entry on the stack.
>
> Hi C
On Jan 16 16:44, Corinna Vinschen wrote:
> Hi Marco,
>
> On Jan 16 15:23, Marco Atzeri wrote:
> > On 1/15/2015 10:34 AM, Corinna Vinschen wrote:
> > >Bottom line, you should be able to fetch the original return address by
> > >printing the value at
> > >
> > > *(void*)_my_tls->stackptr
> > >
> >
On Jan 16 16:44, Corinna Vinschen wrote:
> On Jan 16 15:23, Marco Atzeri wrote:
> > Attached patch that allows tracking of original caller,
> > for the 4 memory allocation calls.
>
> Thanks for the patch, but it won't work nicely either this way. The
> problem is that, in theory, the code has to
On 1/16/2015 5:22 PM, Corinna Vinschen wrote:
On Jan 16 16:44, Corinna Vinschen wrote:
On Jan 16 15:23, Marco Atzeri wrote:
Attached patch that allows tracking of original caller,
for the 4 memory allocation calls.
Thanks for the patch, but it won't work nicely either this way. The
problem i
On Jan 16 18:33, Marco Atzeri wrote:
> On 1/16/2015 5:22 PM, Corinna Vinschen wrote:
> >On Jan 16 16:44, Corinna Vinschen wrote:
> >>On Jan 16 15:23, Marco Atzeri wrote:
> >>>Attached patch that allows tracking of original caller,
> >>>for the 4 memory allocation calls.
> >>
> >>Thanks for the patc
