https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112020-08-31T21:22:50ZRuby Issue Tracking SystemRuby master - Bug #15178: Wrong paramaters passing to pthread_setname_np(3)https://bugs.ruby-lang.org/issues/15178?journal_id=873282020-08-31T21:22:50Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><p>I agree with your analysis. Looking at the NetBSD man page for pthread_setname_np (<a href="https://netbsd.gw.com/cgi-bin/man-cgi?pthread_setname_np++NetBSD-current" class="external">https://netbsd.gw.com/cgi-bin/man-cgi?pthread_setname_np++NetBSD-current</a>), the format string is clearly the 2nd argument and not the third. The only reason this hasn't caused problems is that few thread names are going to use printf(3) format specifiers. I've added a pull request to fix this: <a href="https://github.com/ruby/ruby/pull/3492" class="external">https://github.com/ruby/ruby/pull/3492</a></p> Ruby master - Bug #15178: Wrong paramaters passing to pthread_setname_np(3)https://bugs.ruby-lang.org/issues/15178?journal_id=873372020-09-01T14:16:45Zjeremyevans (Jeremy Evans)code@jeremyevans.net
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Applied in changeset <a class="changeset" title="Fix pthread_setname_np arguments on NetBSD The previous attempt to fix this in b87df1bf243074edb..." href="https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/be9dbe1c3eb4bb4cab0bdc42a91ef425bb1eaddd">git|be9dbe1c3eb4bb4cab0bdc42a91ef425bb1eaddd</a>.</p>
<hr>
<p>Fix pthread_setname_np arguments on NetBSD</p>
<p>The previous attempt to fix this in<br>
b87df1bf243074edb2e6cc8a24bc00df81cebf3c reversed the argument<br>
order instead of just fixing the quote escaping.</p>
<p>From Takahiro Kambe.</p>
<p>Fixes [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Wrong paramaters passing to pthread_setname_np(3) (Closed)" href="https://bugs.ruby-lang.org/issues/15178">#15178</a>]</p> Ruby master - Bug #15178: Wrong paramaters passing to pthread_setname_np(3)https://bugs.ruby-lang.org/issues/15178?journal_id=873582020-09-02T09:56:20Znagachika (Tomoyuki Chikanaga)nagachika00@gmail.com
<ul><li><strong>Backport</strong> changed from <i>2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN</i> to <i>2.5: UNKNOWN, 2.6: REQUIRED, 2.7: REQUIRED</i></li></ul> Ruby master - Bug #15178: Wrong paramaters passing to pthread_setname_np(3)https://bugs.ruby-lang.org/issues/15178?journal_id=896592020-12-31T06:37:28Znagachika (Tomoyuki Chikanaga)nagachika00@gmail.com
<ul><li><strong>Backport</strong> changed from <i>2.5: UNKNOWN, 2.6: REQUIRED, 2.7: REQUIRED</i> to <i>2.5: UNKNOWN, 2.6: REQUIRED, 2.7: DONE</i></li></ul><p>ruby_2_7 16930b254b4e5397759d6b42845b495041b71321 merged revision(s) be9dbe1c3eb4bb4cab0bdc42a91ef425bb1eaddd.</p> Ruby master - Bug #15178: Wrong paramaters passing to pthread_setname_np(3)https://bugs.ruby-lang.org/issues/15178?journal_id=912972021-04-04T23:30:53Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Backport</strong> changed from <i>2.5: UNKNOWN, 2.6: REQUIRED, 2.7: DONE</i> to <i>2.5: UNKNOWN, 2.6: DONE, 2.7: DONE</i></li></ul><p>ruby_2_6 r67923 merged revision(s) be9dbe1c3eb4bb4cab0bdc42a91ef425bb1eaddd.</p>