http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind

> On Jun 2, 2015, at 2:38 PM, Tuan Nguyen <[email protected]> wrote:
> 
> Thanks Matt!
> 
> It works now but there is issue of memory occur: 
> 
> PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably 
> memory access out of range
> [3]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> [3]PETSC ERROR: or see 
> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[3]PETSCERROR:
>  or try http://valgrind.org on linux or man libgmalloc on Apple to find 
> memory corruption errors
> [3]PETSC ERROR: likely location of problem given in stack below
> [3]PETSC ERROR: ---------------------  Stack Frames 
> ------------------------------------
> [3]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
> [3]PETSC ERROR:       INSTEAD the line number of the start of the function
> [3]PETSC ERROR:       is given.
> [3]PETSC ERROR: --------------------- Error Message 
> ------------------------------------
> [3]PETSC ERROR: Signal received!
> 
> ​I am planning to find where in the code the error occur by using valgrind. 
> Could you please let me know how to do this? 
> 
> Here is the command I use to run the code:
> 
> /opt/openmpi/mpirun -np 10 ./fvom --casename=lake>info.dat
> ​
> ​Thanks,​
> 
> 
> 
> 
> On Tue, Jun 2, 2015 at 1:30 PM, Matthew Knepley <[email protected]> wrote:
> On Tue, Jun 2, 2015 at 12:17 PM, Tuan Nguyen <[email protected]> wrote:
> Dear all,
> 
> I installed PETSC 3.1-p8 library. I am trying compile the fortran code link 
> to Petsc but there is message saying about target file as follow:
> 
> ​​petsc-3.1-p8-openmpi/conf/rules:120: *** target file `clean' has both : and 
> :: entries.  Stop.
> 
> ​In my "makefile" I added double-colon to target clean but it will bring me 
> to another error message:
> ​
> /home/petsc-3.1-p8-openmpi/conf/rules:299: warning: overriding commands for 
> target `.c.o'
> makefile:39: warning: ignoring old commands for target `.c.o'
> /home/petsc-3.1-p8-openmpi/linux-gnu-c-debug/conf/petscrules:31: warning: 
> overriding commands for target `.F.o'
> makefile:42: warning: ignoring old commands for target `.F.o'
> /home/petsc-3.1-p8-openmpi/linux-gnu-c-debug/conf/petscrules:31: warning: 
> overriding commands for target `.F90.o'
> makefile:47: warning: ignoring old commands for target `.F90.o'
> /bin/rm -f *.o *.mod *.f90
> 
> ​Could any one help me?
> 
> In your makefile, you have rules for .c.o, etc. You either use the PETSc 
> makefiles, which define these rules, or
> use your own rules, in which case just use the conf/variables file which 
> defines our make vars.
> 
>    Matt
>  
> Thanks,​
> 
> Tuan
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments 
> is infinitely more interesting than any results to which their experiments 
> lead.
> -- Norbert Wiener
> 
> 
> 
> -- 
> 
> Tuan Nguyen
> Michigan State University
> East Lansing, MI. 48823
> 

Reply via email to