Karsten Hilbert <karsten.hilb...@gmx.net> writes: > ... > 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. -- https://mail.python.org/mailman/listinfo/python-list
