We just found out that we have two different learning tasks (one is segmentation, one classification) that are giving segfault in the exact same place, so the possibility that this is a side-effect of changes of memory locations (e.g. due to bad indexing) from other parts of the code is less likely (if this is what you refer to “different places that the erroring line”).