https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69650
--- Comment #50 from Bernd Schmidt <bernds at gcc dot gnu.org> --- The 0xa5 bytes probably come from ggc-page, which tries to poison freed memory. This does suggest that there's a use-after-free issue here. At the step after "p map", try "watch -l map->to_file" followed by "run", which should get you to the point where the memory is overwritten.
