I wonder if there is a good way to find the source code that causes a heap corruption error, given the memory address of the data that was written \'outside\' the allocated
If the error is reproducible and the corrupted address is always the same, you can put a data breakpoint to stop the program when writing at this address.