<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>"The ins and outs of signal handlers" by Peter Edwards</title>
        <link>https://tube.mucs.club/videos/watch/2ee7ce91-e7c5-44b2-91a4-f2f77be38154</link>
        <description>Abstract: Signals are an ancient mechanism of communicating asynchronous events to C programs. Signals make it so that functions appear to magically get invoked spontaneously as your program runs, with just the odd system call returning and setting errno to EINTR as the only side effect. I'll try and demystify the mechanism by which signal handlers get invoked - how we go from executing your main program, to executing a signal handler, and getting back to where you were interrupted. Slides: https://peadar.github.io/signals/</description>
        <lastBuildDate>Wed, 02 Sep 2026 06:11:51 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://tube.mucs.club</generator>
        <image>
            <title>"The ins and outs of signal handlers" by Peter Edwards</title>
            <url>https://tube.mucs.club/client/assets/images/icons/icon-1500x1500.png</url>
            <link>https://tube.mucs.club/videos/watch/2ee7ce91-e7c5-44b2-91a4-f2f77be38154</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://tube.mucs.club/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://tube.mucs.club/feeds/video-comments.xml?videoId=2ee7ce91-e7c5-44b2-91a4-f2f77be38154" rel="self" type="application/rss+xml"/>
    </channel>
</rss>