Debugging an evil Go runtime bug (2017)

Posted by pmoriarty on Tuesday November 05, 2019 @01:10AM
from the marcan.st dept.

https://marcan.st/2017/12/debugging-an-evil-go-runtime-bug/

( 6 comments | 46 points | on HN )

Re:Debugging an evil Go runtime bug (2017) by jchw on Tuesday November 05, 2019 @03:38PM (#21456418)

Hector Marcan is a wizard. The “hash based” differential compilation technique is inspirational.

[ Parent | on HN ]

Re:Debugging an evil Go runtime bug (2017) by dang on Tuesday November 05, 2019 @01:13AM (#21450114)

Discussed at the time: https://news.ycombinator.com/item?id=15845118

[ Parent | on HN ]

Re:Debugging an evil Go runtime bug (2017) by rgoulter on Tuesday November 05, 2019 @08:54AM (#21452334)

A highlight from the comments:

>> That was Captain Ahab level persistence. I wonder how long it took him.

> I was one of the spectators on the Prometheus thread. It took him 2 days. It was insane

[ Parent | on HN ]

Re:Debugging an evil Go runtime bug (2017) by throwaway40324 on Tuesday November 05, 2019 @06:21PM (#21457938)

After slowly reading this with inquisitiveness and looking up a lot of things, I'm really curious to know the years / level of low level systems programming and experience that this kind of debugging and write up takes. I am humbled by the knowledge of the OP, and deem myself not worthy!

[ Parent | on HN ]

Re:Debugging an evil Go runtime bug (2017) by sly010 on Wednesday November 06, 2019 @09:51AM (#21463107)

Someone should publish a book of these stories. I would buy it.

[ Parent | on HN ]

Re:Debugging an evil Go runtime bug (2017) by Exuma on Tuesday November 05, 2019 @02:12PM (#21455589)

This is nuts

[ Parent | on HN ]