Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
1–10 of 50 posts
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#2(2017)
Previous discussion: https://news.ycombinator.com/item?id=15845118
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#3This is honestly wild. 99% of devs would have found a work around and moved on. Going so far as to create a multi-kernel test bench to narrow down the source of the instability is a level of dedication I have not personally seen, and I respect it.
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#4This is honestly wild. 99% of devs would have found a work around and moved on. Going so far as to create a multi-kernel test bench to narrow down the source of the instability is a level of dedication I have not personally seen, and I respect it.
By the same token, you might be the first person I have ever seen give respect to the 1x developer. I respect that. We could no doubt all learn a thing or two from the 1x developer that doesn't rush through everything with quick solutions.
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#5This is honestly wild. 99% of devs would have found a work around and moved on. Going so far as to create a multi-kernel test bench to narrow down the source of the instability is a level of dedication I have not personally seen, and I respect it.
Marcan is an beast, this guy really loves to go down the rabbit holes.
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#6This is honestly wild. 99% of devs would have found a work around and moved on. Going so far as to create a multi-kernel test bench to narrow down the source of the instability is a level of dedication I have not personally seen, and I respect it.
By the same token, you might be the first person I have ever seen give respect to the 1x developer. I respect that. We could no doubt all learn a thing or two from the 1x developer that doesn't rush through everything with quick solutions.
If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very quick going through the rabbit hole.
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#7Earlier quoted context omitted.
By the same token, you might be the first person I have ever seen give respect to the 1x developer. I respect that. We could no doubt all learn a thing or two from the 1x developer that doesn't rush through everything with quick solutions.
If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very quick going through the rabbit hole. [1]: https://github.com/prometheus/node_exporter/issues/730
[flagged]
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#8I feel like I still didnt fully understand what's going on here. Is the following correct? "Threads hava a 'canonical' stack that the OS auto-grows for you as you use more of it. But you can also create your own stack by putting any value you want in RSP. This is what the Go program did, and the vDSO, assuming it ran on an auto-growing stack, tried to probe it, which lead to corruption."
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#9Earlier quoted context omitted.
By the same token, you might be the first person I have ever seen give respect to the 1x developer. I respect that. We could no doubt all learn a thing or two from the 1x developer that doesn't rush through everything with quick solutions.
If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very quick going through the rabbit hole. [1]: https://github.com/prometheus/node_exporter/issues/730
From the outside looking in, that's mind blowing.
Re: Debugging an evil Go runtime bug: From heat guns to kernel compiler flags (2017)
#10Earlier quoted context omitted.
If you check the issue[1] he reported the crash on November 7th and reported the issue is related to gcc and the kernel on November 8th. At least he was very quick going through the rabbit hole. [1]: https://github.com/prometheus/node_exporter/issues/730
[flagged]
Emm, 10x developer is a myth. The real 10x developer is the one that creates such an infrastructure/libraries/culture that enables 10 other engineers to move fast. The 10x developer is not the person that is 10x faster than other developers on the code base simply because they can hold the spaghetti code they wrote in their head.