<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Misuse of setjmp in DCTStream"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63067#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Misuse of setjmp in DCTStream"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63067">bug 63067</a>
from <span class="vcard"><a class="email" href="mailto:rodrigorivascosta@gmail.com" title="rodrigo <rodrigorivascosta@gmail.com>"> <span class="fn">rodrigo</span></a>
</span></b>
<pre><span class="quote">> But now that I read the 'longjmp(3p)' [2] with more detail, I think that
> there are bigger problems ahead... Note the following quote:</span >
Replying to myself, that 'longjmp' problem does not exist at all! I've reread
the code of DCTStream.cc and every time a jpeg_* function is called, there is a
call to 'setjmp' in that very same function, so the call to 'longjmp' will
always be valid.
The original corrections about 'setjmp' still stands, of course.</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>