right list for SIGABRT python binary question ?

[Karsten Hilbert]

On Fri, Nov 03, 2017 at 07:31:56AM +0100, dieter wrote:

> > I have posted backtraces taken from the address being
> > watched. Does that help any at all ?
> 
> Only in the case that the error is "local", i.e. detected
> (quite) immediately.
> 
> You might be in this case as you have observed that the address
> is stable after library preload. Thus, it might not be a heap
> address but one associated with one of the libraries. Such
> a memory block should never be "freed". The backtrace would allow
> you to determine the library affected. Obtain its source. Recompile
> with symbols and try to find out where this memory block comes from.

Dieter, thanks for taking the time to explain the general
procedure. However, recompiling a library and trying to find
out where given block of memory comes from is way beyond
skills. I fear I have reached the end of what I can do.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346