More info on the Parallel Inspector at: http://software.intel.com/en-us/articles/intel-parallel-inspector/
If is an real leak I think ,using an tool analyzer ,result no value.
(My answer is for C/C++,i hope it would be value same with the Fortran)
For help add (ipo) flag for find more precise where fault point, could be an halt blank without message
After if possible increase progressive by step reserved memory or the size array and other var for unlock
this halt blank result.
With flto (gnu gcc) or ipo or other flag for reorganize the group of the functions in the object, you could discovering an variable memory responsible is moved wrong to an other variable no relation.
Also trace just point show (value variable) screen
it could be result some values added with extended incomprehensible characters without relation or NaN
The leak problem is complex ,more easy to make same (enlarge size reserved variable
you rewrite forced differently resulting the customer scream to you, is too expensive..... is theft ....
About (hater) i think it should not exist with programming sector.
Almost 28 years programming majority Unix side and i consider always Team Microsoft are my friends.
When i have problem C/CPP or other i have the better help is possible received from them
without, is judgment choice my O/S operated .
If you feed your family, today probably,thanks, to them existed history..
Sorry same you having wrote I supposed that your major activity is professional programming.
For activity that you denounced,yes it could be more appropriated to use O/S Unix side.
The performance depend library quality , in imbrication with your task
Yes O/S Microsoft side could be slow, if too services
superficial are loaded for nothing.
With adjustment of (daemon or services) really necessary the two systems could given difference
variation 7/15 % ,unfortunately not an miracle with one of two.
With true real leak ,I have use already different supposed appropriate tools without never obtain,
an really effective result . I finish always increase certain size
declaration, for forced kernel to changing the location of memory incriminated.
Fortunately real leak is very rare ,often , is rather the fault programming,where all tools disposed
is more effective for solving.
I use also for personal Linux: Debian 5.0 x86_64 ,with added new build GCC 4.5.1
I think difficult to find better....
The Code Project is an excellent programmer resource.
Also consider SourceForge.net http://sourceforge.net/projects/memdebug/
As recently indicated, our new thread and memory error checker, the Intel Inspector XE 2011 is now released. The tool is part of the Intel Parallel Studio XE 2011 for Linux*.
For more details on the Intel Inspector XE 2011, please visit http://software.intel.com/en-us/articles/intel-inspector-xe/
For more information on Intel Parallel Studio XE 2011, please visit http://software.intel.com/en-us/articles/intel-parallel-studio-xe/