<html>#2832: possible race condition in LoopControl
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p><span class="ap-mention" data-atlassian-id="557058:d079f9c2-ad27-47b2-bf4b-ecc6bbe288b0">@Yosef Zlochower</span> reported an issue where SEGFAULTs are triggered from within LoopControl.</p>
<p>I can reproduce this using the thornlist and parameter file that Yosef provided. I use the attached option list, where using <code>-std=gnu++11</code> instead of <code>-std=c++17 -D_GNU_SOURCE</code> is required for the issue to show up for me.</p>
<p>I run using </p>
<div class="codehilite"><pre><span></span><code><span>export OMP_NUM_THREADS=2</span>
<span>exe/cactus_yosef test.par</span>
</code></pre></div>
<p>and the CPU on my workstation is a “12th Gen Intel(R) Core(TM) i7-12700”</p>
<p><table><tr><td>attachment:</td><td><a href="https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2832/attachments/OptionList">OptionList</a></td></tr>
</table></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2832/possible-race-condition-in-loopcontrol'>https://bitbucket.org/einsteintoolkit/tickets/issues/2832/possible-race-condition-in-loopcontrol</a></p>
</html>