On Mon, Oct 23, 2017 at 03:26:18PM +0200, Thomas Jollans wrote: > >> It points to a memory corruption. > > > > While running valgrind and friends is beyond my capabilitis I > > have run the problem through gdb to at least obtain a stack > > trace to see what gives: > > I wouldn't read too much into that. You know that somehow some memory > got corrupted. You know at which point Python trips over the error - but > that doesn't really tell you anything about how the memory initially got > corrupted.
Thanks, I know. However, I am grasping for straws here since I am unable to "properly" debug the python binary as such. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- https://mail.python.org/mailman/listinfo/python-list
