<div class="gmail_quote">On Fri, Jun 17, 2011 at 12:05, Alexander Grayver <span dir="ltr"><<a href="mailto:agrayver@gfz-potsdam.de">agrayver@gfz-potsdam.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">What is ABI?</div></blockquote><div><br></div><div><br></div><div>Application Binary Interface, basically the assembly-level calling semantics. If the tests run successfully, then this is not the problem.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im"></div>
Both examples work without crashing. Pretty weird...<br></div></blockquote><div><br></div><div>One more to try: mat/examples/tests/ex16f90.F</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
I can tell more. I found place in my code, just different fortran
module, where VecGetArrayF90 works both on seq and mpi vectors.</div></blockquote><div><br></div><div>This call works from one Fortran module, but not from another? I suspect stack corruption, perhaps from something as simple as the wrong number of arguments to an earlier call. (Fortran having nearly worthless type checking.)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im">What API do you mean exactly?</div></div></blockquote>
</div><br><div>The non-F90 VecGetArray() and MatGetArray(). But if MatGetArrayF90() is working when called in a different context, then this shouldn't be necessary.</div>