<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault loading War Thunder"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92850#c43">Comment # 43</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault loading War Thunder"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92850">bug 92850</a>
from <span class="vcard"><a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> <span class="fn">Roland Scheidegger</span></a>
</span></b>
<pre>(In reply to bellamorte42 from <a href="show_bug.cgi?id=92850#c42">comment #42</a>)
<span class="quote">> I'm not sure I follow your logic. The code compiles fine on its own. The
> code compiles fine under a variety of optimizations. A single optimization
> causes a segfault. =it's the codes fault?</span >
Why not? Things like that are quite common. For instance when using undefined
values it can easily work with some compiler options but not others. Or doing
some kind of reading/writing past array bounds. All bets are off with such code
(and valgrind would catch both these errors). Not saying that's necessarily the
case here but I don't see any evidence to the contrary neither...</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>