<div class="gmail_quote">On Fri, Oct 21, 2011 at 11:57, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":251">1) Syscall param writev(vector[...]) points to uninitialised byte(s)<br>
-> tribbered by MatPartitioningApply, then leading deep into ParMetis<br></div></blockquote><div><br></div><div>If we're lucky, this has been fixed in the latest ParMetis release. (PETSc can use it, but not all the external packages can yet. We're patching these before using the new release by default.)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":251">
<br>
2) Conditional jump or move depends on uninitialised value(s) -><br>
many times, in VecMin and VecMax and KSPSolve_BCGSL<br>
and<br>
<br>
3) Syscall param writev(vector[...]) points to uninitialised byte(s)<br>
-> just once, in VecScatterBegin triggered by VecCreateGhost on the<br>
'x' vector, which is ghosted.<br>
<br>
Do they pose any serious threats?<br>
<div class="im"><br>
><br>
> Have you tried KSPBCGSL? This is "enhanced Bi-CG-stab" algorithm that is designed to handle certain situations that may cause grief for regular Bi-CG-stab I guess.<br>
><br>
<br>
</div>Thanks for the hint on bcgsl - it works as expected.<br>
<br>
So, do I have a problem in the code or bcgs is unreliable? If the<br>
latter: as a method or as this specific implementation?</div></blockquote></div><br><div>It would be much easier to answer these questions if you sent a test case or showed us how to reproduce the problem with a PETSc example.</div>