<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - pdfsig: Segfault in ~SignatureHandler / double-free"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97149#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - pdfsig: Segfault in ~SignatureHandler / double-free"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97149">bug 97149</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@michael-joost.de" title="Michael Joost <freedesktop@michael-joost.de>"> <span class="fn">Michael Joost</span></a>
</span></b>
<pre>No, this is not a bug of nspr, because subsequent access to freed memory is
most likely a design fault of its users. The only (light) problem of nspr is
that it is debug by default. The DA pattern is most likely intended to identify
such invalid use.
Whether the double-destroy is a genuine problem of nss or pdfsig is not clear
to me; don't know whether it is intended/allowed by nss to manage the same cert
object in several lists. There is a condition in nss testing for NULL, which
prevents the crash without the DA pattern, but this smells for problems.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>