Re: gfortran problem
- From: Tobias Burnus <burnus@xxxxxxxx>
- Date: Mon, 31 Mar 2008 10:05:33 -0700 (PDT)
On Mar 31, 6:52 pm, rudra <bnrj.ru...@xxxxxxxxx> wrote:
*** glibc detected *** /matsc/students/Rudra/Recursion/Real/run.out:[...]
double free or corruption (out): 0xb7f79008 ***
#6 0x0024e0c1 in _gfortran_internal_free () from /usr/lib/
libgfortran.so.1
#7 0x0804a075 in coefficient_ (istart=@0xbf8b1eb4, lorbit=@0xbf8b1eac,
nrec=@0xbf8b1ea8, nsite=@0xbf8b1efc,
nmax=@0xbf8b1eb0, nn=@0xbf8b1ef8, cmat=0xbf8b1e50, dmat=0xbf8b1e08) at
coeff.f90:5
#8 0x0804af1b in MAIN__ () at main.f90:64
#9 0x0804af47 in main ()
(gdb)
can anybody tell me whats wrong? gfortran is working well elsewhere
Not without further information such as knowing how "coefficient" in
coeff.f90 looks like. If you use POINTER then it could well be a
programming error, if not it could be a gfortran bug.
Regarding the latter, it would like to know the system (target) and
the version of gfortran (run: gfortran -v).
Additionally, if you have "valgrind", run you program in valigrind.
This provides often a better clue where things go wrong. Sometimes
things go wrong but surface never or only much later. Run also the
ifort program in "valgrind", even though it does not crash it could
well have the same problem.
Tobias
.
- Follow-Ups:
- Re: gfortran problem
- From: rudra
- Re: gfortran problem
- References:
- gfortran problem
- From: rudra
- gfortran problem
- Prev by Date: gfortran problem
- Next by Date: Re: gfortran problem
- Previous by thread: gfortran problem
- Next by thread: Re: gfortran problem
- Index(es):
Relevant Pages
|
