<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for kettenis</title>
    <link>http://www.advogato.org/person/kettenis/</link>
    <description>Advogato blog for kettenis</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Sat, 25 May 2013 14:24:17 GMT</pubDate>
    <item>
      <pubDate>Sun, 23 Apr 2000 17:46:44 GMT</pubDate>
      <title>23 Apr 2000</title>
      <link>http://www.advogato.org/person/kettenis/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/kettenis/diary.html?start=0</guid>
      <description>I spent the last few days on improving debugging
multithreaded programs with GDB under Linux.  I now know
more of more of the Linux threads implementation than I've
ever wanted.  And my conclusion is that it's completely
broken.  There is no other way to stop the program being
debugged than to send a SIGSTOP to every sub-process in the
program.  And of course the kernel doesn't even tell you
what those sub-processes are!  Next time Linus starts
telling that clone() is all you need ...</description>
    </item>
  </channel>
</rss>
