<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - crash because of null string on solaris"
href="https://bugs.freedesktop.org/show_bug.cgi?id=55607#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - crash because of null string on solaris"
href="https://bugs.freedesktop.org/show_bug.cgi?id=55607">bug 55607</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>Sorry for ignoring this. There was shortage of maintainer time prior to last
November.
This particular change seems strange to me. "git grep pa_thread_new" indicates
that threads are always created with a name, so t->name should never be NULL.
As for handling possibly-NULL strings in printf arguments in general, we have
pa_strnull(), which may be in many cases more appropriate than patching
string-returning functions to never return NULL.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>