<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bugs on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/bugs/</link>
    <description>Recent content in Bugs on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 22 Jun 2018 13:39:39 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/bugs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The main thread name and process name are the same thing on Linux!</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/linux-main-thread-name/</link>
      <pubDate>Fri, 22 Jun 2018 13:39:39 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/linux-main-thread-name/</guid>
      <description>On typical days, we software engineers are usually stuck due to head scratching bugs, instead of actually writing interesting software. I had made some small changes and suddenly our end-to-end tests were timing out, with no useful clues. The harness emits a crazy number of log lines, so digging through them was difficult.&#xA;Fortunately, the problem was easily reproduceable on a local VM and with some piecemeal commenting I was able to isolate it to changing the thread name of the main thread, that I had done for some debugging information.</description>
    </item>
  </channel>
</rss>
