[petsc-users] About the ./configure of petsc and mpi
w_ang_temp
w_ang_temp at 163.com
Sat Jun 2 09:11:18 CDT 2012
Hello, Jed
I use gdb to debug it.
(1)The source code(The line number is add by me.Line 125 and 127 are added right now for debugging ):
............
121 open(50,FILE='check.out')
122 open(LSS,FILE='select.dat')
123 C open(LH,FILE='select1.dat',FORM='UNFORMATTED')
124 open(LR,FILE='initials.dat')
125 write(*,*) 'test1'
126 open(LTR,FILE='trapdoor.dat')
127 write(*,*) 'test2'
(2) Debug information:
(gdb) break 124
Breakpoint 1 at 0x804bb42: file ex4f.F, line 124.
(gdb) run
Starting program: /home/geo/project/temp/8-little-9-2716/tutorials/ex4f
[Thread debugging using libthread_db enabled]
Breakpoint 1, gleaves () at ex4f.F:124
124 open(LR,FILE='initials.dat')
(gdb) n
125 write(*,*) 'test1'
(gdb) n
test1
126 open(LTR,FILE='trapdoor.dat')
(gdb) n
forrtl: severe (32): invalid logical unit number, unit -1208035944, file unknown
Image PC Routine Line Source
libirc.so 00AC3470 Unknown Unknown Unknown
libirc.so 00AC2011 Unknown Unknown Unknown
libifcore.so.5 00BD066B Unknown Unknown Unknown
libifcore.so.5 00B5A178 Unknown Unknown Unknown
libifcore.so.5 00B70CF4 Unknown Unknown Unknown
ex4f 0804BC6B Unknown Unknown Unknown
ex4f 0804B904 Unknown Unknown Unknown
libc.so.6 00C48BD6 Unknown Unknown Unknown
ex4f 0804B811 Unknown Unknown Unknown
Program exited with code 040.
(gdb)
(3)From the information above, it stops in 126 and can not go to line 127.
Thanks.
Jim
>在 2012-06-02 21:11:05,"Jed Brown" <jedbrown at mcs.anl.gov> 写道:
>On Sat, Jun 2, 2012 at 7:02 AM, w_ang_temp <w_ang_temp at 163.com> wrote:
>Hello,
> I reconfigure the mpi and petsc today. I want to use ifort as the compiler.
>And there is a problem.
> Before I reconfigure them, both compiling and running are ok (1.make ex4f;
>2.mpiexec -n 2 ./ex4f;The name 'ex4f' is my project name, not the petsc
>example name).And I have done lots of work before.Since I think the project
>is inefficient, I want to use ifort.
> After the reconfiguration, the compiling seems ok(make ex4f) and I can get
>the executable file. But when I run it(mpiexec -n 2 ./ex4f), it does not work
>('forrtl: severe (32): invalid logical unit number, unit -1215421032, file unknown').
>Show us the full stack trace (the full PETSc error message is good, a gdb stack trace would be better). It's quite possible that that you have >some code that is not standards compliant, thus it behaves differently with different compilers.
>Besides, both compiling and running are ok when I test the petsc examples.
> Before I reconfigure them, the configurations are as follows:
> mpi: ./configure --prefix=/home/geo/soft/mpich2
> PETSc: ./configure --download-f-blas-lapack=1
> And now the configurations are the following:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120602/002c00a8/attachment-0001.html>
More information about the petsc-users
mailing list