Help needed to identify golang fork / memory corruption issue on FreeBSD

[Konstantin Belousov]

On Mon, Mar 27, 2017 at 07:17:20PM +0100, Steven Hartland wrote:
> Here's the output after its logged the errors.
> 
> procstat -v 36159
>    PID              START                END PRT  RES PRES REF SHD FLAG 
> TP PATH
> 36159           0x400000           0x70d000 r-x  308  588 3   1 CN-- vn 
> /root/golang/src/test5/test5
> 36159           0x70d000           0x94e000 r--  248  588 3   1 CN-- vn 
> /root/golang/src/test5/test5
> 36159           0x94e000           0x985000 rw-   31    0 1   0 C--- vn 
> /root/golang/src/test5/test5
> 36159           0x985000           0x9a8000 rw-   18   18 1   0 C--- df
> 36159        0x80094e000        0x8009ee000 rw-   35   35 1   0 C--- df
> 36159        0x8009ee000        0x800abe000 rw-   28   28 1   0 C--- df
> 36159        0x800abe000        0x800ace000 rw-   16   16 1   0 C--- df
> 36159        0x800ace000        0x800b0e000 rw-    2    2 1   0 CN-- df
> 36159        0x800b0e000        0x800b4e000 rw-    2    2 1   0 C--- df
> 36159        0x800b4e000        0x800b8e000 rw-    2    2 1   0 C--- df
> 36159        0x800b8e000        0x800c0e000 rw-    3    3 1   0 C--- df
> 36159        0x800c0e000        0x800c4e000 rw-    2    2 1   0 C--- df
> 36159        0x800c4e000        0x800c8e000 rw-    1    1 1   0 CN-- df
> 36159        0x800c8e000        0x800cce000 rw-    1    1 1   0 C--- df
> 36159        0x800cce000        0x800d0e000 rw-    1    1 1   0 CN-- df
> 36159       0xc000000000       0xc000001000 rw-    1    1 1   0 CN-- df
> 36159       0xc41fff0000       0xc41fff8000 rw-    3    3 1   0 CN-- df
> 36159       0xc41fff8000       0xc420200000 rw-  258  258 1   0 C--- df
> 36159     0x7ffffffdf000     0x7ffffffff000 rwx    2    2 1   0 C--D df
> 36159     0x7ffffffff000     0x800000000000 r-x    1    1 38   0 ---- ph
> 
> I've left it running in case you want any more info.

At which address the word is located where an invalid value was detected ?