Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mstdn.social/users/jschauma/statuses/113348730576478746">Jan Schaumann (jschauma@mstdn.social)'s status on Monday, 04-Nov-2024 03:38:15 JST</a><a href="https://mstdn.social/@jschauma" title="jschauma@mstdn.social"><img src="https://gnusocial.jp/avatar/110518-48-20230331194031.webp" width="48" height="48" alt="Jan Schaumann" style="position: absolute; left: 0; top: 0;">Jan Schaumann</a><div><a href="https://mstdn.social/@jschauma/113334832734671246" rel="in-reply-to">in reply to</a></div></section><article><p>Advanced <a href="https://mstdn.social/tags/Programming" rel="tag">#Programming</a> in the <a href="https://mstdn.social/tags/UNIX" rel="tag">#UNIX</a> Environment</p><p>Week 7, Reentrant and Interrupted Functions</p><p>We learn that only functions guaranteed to be async-signal-safe can safely be used in signal handlers (see sigaction(2)), as well as what happens when we are interrupted while blocking on certain I/O. (Note: some Unix versions provide reentrant "_r" versions of otherwise non-reentrant functions (see e.g., ctime_r(3)). Both are distinct from thread-safe functions.)</p><p><a href="https://youtu.be/0GRLhpMao3I" rel="nofollow noreferrer">https://youtu.be/0GRLhpMao3I</a></p><p><a href="https://mstdn.social/tags/apue" rel="tag">#apue</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3930727#notice-7680041">In conversation</a><time datetime="2024-11-04T03:38:15+09:00" title="Monday, 04-Nov-2024 03:38:15 JST">about 19 days ago</time> <span>from <span><a href="https://mstdn.social/@jschauma/113348730576478746" rel="external" title="Sent from mstdn.social via ActivityPub">mstdn.social</a></span></span><a href="https://mstdn.social/@jschauma/113348730576478746">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3404658">Untitled attachment</a></label><br><a href="https://media.mstdn.social/media_attachments/files/113/348/729/427/852/376/original/9b957364c20e5b36.png" rel="external">https://media.mstdn.social/media_attachments/files/113/348/729/427/852/376/original/9b957364c20e5b36.png</a></li><li><article><header><img height="128" width="128" src="https://gnusocial.jp/thumbnail/3404661?w=128&amp;h=128"><h5><a href="https://www.youtube.com/watch?v=0GRLhpMao3I&amp;feature=youtu.be">Advanced Programming in the UNIX Environment: Week 07, Segment 5 - Reentrant &amp; interrupted functions</a></h5><div> from <span>cs631apue</span></div></header><div>With this video lecture, we will conclude our coverage of Unix signals, by looking at what happens when we call unsafe functions from within the signal handl...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jan Schaumann (jschauma@mstdn.social)'s status on Monday, 04-Nov-2024 03:38:15 JST Jan Schaumann
in reply to
Advanced #Programming in the #UNIX Environment
Week 7, Reentrant and Interrupted Functions
We learn that only functions guaranteed to be async-signal-safe can safely be used in signal handlers (see sigaction(2)), as well as what happens when we are interrupted while blocking on certain I/O. (Note: some Unix versions provide reentrant "_r" versions of otherwise non-reentrant functions (see e.g., ctime_r(3)). Both are distinct from thread-safe functions.)
https://youtu.be/0GRLhpMao3I
#apue
In conversationabout 19 days ago from mstdn.socialpermalink
Attachments
1. Untitled attachment
  https://media.mstdn.social/media_attachments/files/113/348/729/427/852/376/original/9b957364c20e5b36.png
2. Advanced Programming in the UNIX Environment: Week 07, Segment 5 - Reentrant & interrupted functions
  from cs631apue
  With this video lecture, we will conclude our coverage of Unix signals, by looking at what happens when we call unsafe functions from within the signal handl...

Public

Embed Notice

HTML Code

Corresponding Notice