Re: Stack corruption and memory leak problems in c++/Fortran application
- From: "Colin Watters" <qolin.see_signature@xxxxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 07:47:28 -0000
"Anndy" <see.nits@xxxxxxxxx> wrote in message
news:1193812383.968907.94420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello Folks,
I am facing problem in a Porting project(HP-Unix->Windows XP(64 bit))
where there are lots of C++->Fortran and Fortran->C++ calls.
There are some thousands of files including FORTRAN and C++ code.
After performing few operation which involves lot of FORTRAN->C++ and C
++->FORTRAN calling, application gives stack overflow error or behaves
unexpectedly.
one more thing which i have noticed is, whenever i am making a call to
a FORTRAN function there is a increase in
application memory by 4Bytes.
compiler c++ : MS Visual Studio 2005 / Compiling for 64 bit
compiler FORTRAN :Intel Fortran Compiler 9.1
Can anyone please help in mentioning the possible problem areas ...
Thankz,
Anndy
The 64-bit issue gets my attention. Having been involved in sorting out the
(relatively easy to spot) problems in our (99.9%) Fortran code when porting
to 64-bit, and knowing that C++ does a lot more with pointers than Fortran,
I would name this as Prime Suspect, in the absense of any other information.
On a 64-bit .exe the pointers have to be stored in 64-bit variables. It may
well be that the C++/Fortran interface code doesn't do this. In which case,
its going to get real tricky.
One way to diagnose if this *IS* the issue: get it working in 32-bit mode
first. I know IVF will compile for either 32-bit or 64-bit depending on
compiler switches, and MSC++ must surely do the same. So use the same PC and
opsys to produce a 32-bit .exe and get the bugs out of that, before
attempting a 64-bit version.
Qolin
Email: my qname at domain dot com
Domain: qomputing
.
- Follow-Ups:
- References:
- Prev by Date: Re: Why gfortran`s stream access is so slow?
- Next by Date: Odd omp_get_wtime()
- Previous by thread: Stack corruption and memory leak problems in c++/Fortran application
- Next by thread: Re: Stack corruption and memory leak problems in c++/Fortran application
- Index(es):
Relevant Pages
|
