[petsc-users] Bug in DAGetGlobalIndicesF90 ?

[Randall Mackie]

Barry,

Calls to VecGetArrayF90 also produce errors:

[7]PETSC ERROR:
------------------------------------------------------------------------
[7]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
probably memory access out of range
[7]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[7]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[7]PETSCERROR:
or try
http://valgrind.org on GNU/
linux and Apple Mac OS X to find memory corruption errors
[7]PETSC ERROR: likely location of problem given in stack below
[7]PETSC ERROR: ---------------------  Stack Frames
------------------------------------
[55]PETSC ERROR:
------------------------------------------------------------------------
[55]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
probably memory access out of range
[55]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[55]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[55]PETSCERROR:
or try
http://valgrind.org on GN
U/linux and Apple Mac OS X to find memory corruption errors
[55]PETSC ERROR: likely location of problem given in stack below


The configure log was sent in a separate email.

Randy Mackie


On Thu, May 6, 2010 at 10:48 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>    Switching this message to petsc-maint at mcs.anl.gov
>
>     Does VecGetArrayF90() work correctly? Please send configure.log to
> petsc-maint at mcs.anl.gov
>
>     Barry
>
> On May 6, 2010, at 12:34 PM, Randall Mackie wrote:
>
> I just upgraded to version 3.1-p2, and have discovered that a call to
> DAGetGlobalIndicesF90 that use to work
> fine is now bombing out with the following message:
>
> [7]PETSC ERROR:
> ------------------------------------------------------------------------
> [7]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
> probably memory access out of range
> [7]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> [7]PETSC ERROR: or see
> 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%5B7%5DPETSC>ERROR: or try
> http://valgrind.org on GNU/
> linux and Apple Mac OS X to find memory corruption errors
> [7]PETSC ERROR: likely location of problem given in stack below
> [7]PETSC ERROR: ---------------------  Stack Frames
> ------------------------------------
> [7]PETSC ERROR: Note: The EXACT line numbers in the stack are not
> available,
> [7]PETSC ERROR:       INSTEAD the line number of the start of the function
> [7]PETSC ERROR:       is given.
> [7]PETSC ERROR: [7] F90Array1dCreate line 52 src/sys/f90-src/f90_cwrap.c
> [7]PETSC ERROR: --------------------- Error Message
> ------------------------------------
> [7]PETSC ERROR: Signal received!
>
>
> Calls to DAGetGlobalIndices (the old non-F90 version) seem to work fine.
> The call to DAGetGlobalIndicesF90
> worked fine in the previous version I was using (3.0.0-p7).
>
>
> Can you take a look and see if you see some problem?
>
> Thanks, Randy Mackie
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20100506/8093f3b0/attachment.htm>