Barry,<br><br>Calls to VecGetArrayF90 also produce errors:<br><br>[7]PETSC ERROR: ------------------------------------------------------------------------<br>[7]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range<br>
[7]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger<br>[7]PETSC ERROR: or see <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[7]PETSC">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[7]PETSC</a> ERROR: or try <a href="http://valgrind.org">http://valgrind.org</a> on GNU/<br>
linux and Apple Mac OS X to find memory corruption errors<br>[7]PETSC ERROR: likely location of problem given in stack below<br>[7]PETSC ERROR: --------------------- Stack Frames ------------------------------------<br>[55]PETSC ERROR: ------------------------------------------------------------------------<br>
[55]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range<br>[55]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger<br>[55]PETSC ERROR: or see <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[55]PETSC">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[55]PETSC</a> ERROR: or try <a href="http://valgrind.org">http://valgrind.org</a> on GN<br>
U/linux and Apple Mac OS X to find memory corruption errors<br>[55]PETSC ERROR: likely location of problem given in stack below<br><br><br>The configure log was sent in a separate email.<br><br>Randy Mackie<br><br><br><div class="gmail_quote">
On Thu, May 6, 2010 at 10:48 AM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><br></div> Switching this message to <a href="mailto:petsc-maint@mcs.anl.gov" target="_blank">petsc-maint@mcs.anl.gov</a><div><br></div><div> Does VecGetArrayF90() work correctly? Please send configure.log to <a href="mailto:petsc-maint@mcs.anl.gov" target="_blank">petsc-maint@mcs.anl.gov</a></div>
<div><br></div><font color="#888888"><div> Barry</div></font><div><div></div><div class="h5"><div><br><div><div>On May 6, 2010, at 12:34 PM, Randall Mackie wrote:</div><br><blockquote type="cite">I just upgraded to version 3.1-p2, and have discovered that a call to DAGetGlobalIndicesF90 that use to work<br>
fine is now bombing out with the following message:<br><br>[7]PETSC ERROR: ------------------------------------------------------------------------<br>
[7]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range<br>[7]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger<br>[7]PETSC ERROR: or see <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal%5B7%5DPETSC" target="_blank">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[7]PETSC</a> ERROR: or try <a href="http://valgrind.org/" target="_blank">http://valgrind.org</a> on GNU/<br>
linux and Apple Mac OS X to find memory corruption errors<br>[7]PETSC ERROR: likely location of problem given in stack below<br>[7]PETSC ERROR: --------------------- Stack Frames ------------------------------------<br>
[7]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,<br>
[7]PETSC ERROR: INSTEAD the line number of the start of the function<br>[7]PETSC ERROR: is given.<br>[7]PETSC ERROR: [7] F90Array1dCreate line 52 src/sys/f90-src/f90_cwrap.c<br>[7]PETSC ERROR: --------------------- Error Message ------------------------------------<br>
[7]PETSC ERROR: Signal received!<br><br><br>Calls to DAGetGlobalIndices (the old non-F90 version) seem to work fine. The call to DAGetGlobalIndicesF90<br>worked fine in the previous version I was using (3.0.0-p7).<br><br>
<br>Can you take a look and see if you see some problem?<br><br>Thanks, Randy Mackie<br>
</blockquote></div><br></div></div></div></div></blockquote></div><br>