News for hackers. Stuff that matters.

A comment on Hunting down a C memory leak in a Go program. Parent comment

Re:Hunting down a C memory leak in a Go program by lostmsu on Saturday October 16, 2021 @12:36AM (#28885583)
valgrind?
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by WalterBright on Saturday October 16, 2021 @04:53AM (#28886494)
I wish. Mine instrumented the source code, not the executable.
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by linkdd on Saturday October 16, 2021 @12:43AM (#28885608)
This was my first guess, but according to wikipedia[0], the author of valgrind is Julian Seward[1].

  [0] - https://en.wikipedia.org/wiki/Valgrind
  [1] - https://en.wikipedia.org/wiki/Julian_Seward
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by leeoniya on Saturday October 16, 2021 @12:50AM (#28885635)
https://en.m.wikipedia.org/wiki/Walter_Bright
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by lostmsu on Saturday October 16, 2021 @12:46AM (#28885620)
Maybe WalterBright is his pseudonym on HN?
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by FridgeSeal on Saturday October 16, 2021 @01:55AM (#28885864)
Fairly sure this is the Walter Bright that wrote the D language, a C++ compiler etc
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by WalterBright on Saturday October 16, 2021 @04:00AM (#28886294)
It was my evil twin. Of course, he claims the evil one is me. Don't listen to him!
[ Parent | on HN ]
Re:Hunting down a C memory leak in a Go program by WalterBright on Saturday October 16, 2021 @04:04AM (#28886305)
No, no, he's the bad one!
[ Parent | on HN ]