News for hackers. Stuff that matters.

A comment on Fix for Golang runtime memory corruption bug. Parent comment

Re:Fix for Golang runtime memory corruption bug by 0x0 on Saturday January 07, 2017 @03:17AM (#13342963)
Well usually you can just update whatever library has the bug and restart your applications, but as I understand this bug will be statically linked in all application binaries so they will all have to be recompiled and redeployed?
[ Parent | on HN ]
Re:Fix for Golang runtime memory corruption bug by Manishearth on Saturday January 07, 2017 @03:31AM (#13343010)
Yes, that's what the grandparent is saying, this is a bug in the runtime, which you can't fix by updating libraries, you have to update the compiler/interpreter (depending on the language).

This is not a unique occurrence.

[ Parent | on HN ]
Re:Fix for Golang runtime memory corruption bug by wonko1 on Saturday January 07, 2017 @03:46AM (#13343058)
I think the original question was querying if the runtime is statically or dynamically linked.

It's also possibly a subtle dig at go, because unlike other languages go does not use dynamic linking, meaning bugs in libraries require recompilation (has positive effects too).

[ Parent | on HN ]
Re:Fix for Golang runtime memory corruption bug by pjmlp on Saturday January 07, 2017 @06:57AM (#13343667)
Yes it does, since Go 1.6.

It just isn't the default compilation mode, you have to explicitly enable it.

[ Parent | on HN ]