Re: Memory leak problem reported with gfortran

2008-02-10 Thread Jerry DeLisle
Corinna Vinschen wrote: On Feb 5 17:23, Jerry DeLisle wrote: Corinna Vinschen wrote: On Feb 4 17:24, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to

Re: Memory leak problem reported with gfortran

2008-02-06 Thread Corinna Vinschen
On Feb 5 17:23, Jerry DeLisle wrote: Corinna Vinschen wrote: On Feb 4 17:24, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the

Re: Memory leak problem reported with gfortran

2008-02-05 Thread Corinna Vinschen
On Feb 4 17:24, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the compiler and I will get back with you off list if I don't spot

Re: Memory leak problem reported with gfortran

2008-02-05 Thread Jerry DeLisle
Corinna Vinschen wrote: On Feb 4 17:24, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the compiler and I will get back with you

Re: Memory leak problem reported with gfortran

2008-02-04 Thread Corinna Vinschen
On Feb 3 11:24, Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 I am not very familiar with the windows environment. Having patched most of the gfortran I/O library in the last 2-3 years I can say that we do a

Re: Memory leak problem reported with gfortran

2008-02-04 Thread Corinna Vinschen
On Feb 3 19:03, Jerry DeLisle wrote: I have continued my testing here and I am seeing this with valgrind on linux. When I was running the 1 loops I did not see these errors roll by upfront initially. ==25454== Conditional jump or move depends on uninitialised value(s) ==25454==at

Re: Memory leak problem reported with gfortran

2008-02-04 Thread Christopher Faylor
On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the compiler and I will get back with you off list if I don't spot the problem. I am fairly certain that Corinna

Re: Memory leak problem reported with gfortran

2008-02-04 Thread Jerry DeLisle
Corinna Vinschen wrote: On Feb 3 11:24, Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 I am not very familiar with the windows environment. Having patched most of the gfortran I/O library in the last 2-3 years I

RE: Memory leak problem reported with gfortran

2008-02-04 Thread Dave Korn
On 04 February 2008 22:25, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the compiler and I will get back with you off list if I

Re: Memory leak problem reported with gfortran

2008-02-04 Thread Jerry DeLisle
Dave Korn wrote: On 04 February 2008 22:25, Christopher Faylor wrote: On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote: The test also appears very clean on Linux. The gfortran library is implemented in C. I need to examine some dumps from the compiler and I will get back with

Re: Memory leak problem reported with gfortran

2008-02-03 Thread Tim Prince
Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 I am not very familiar with the windows environment. Having patched most of the gfortran I/O library in the last 2-3 years I can say that we do a lot of memory

Re: Memory leak problem reported with gfortran

2008-02-03 Thread Greg Chicares
On 2008-02-03 19:24Z, Jerry DeLisle wrote: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 [...] Is this a bug in Cygwin memory management? According to this report (marked in bugzilla as a duplicate): http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35064 a similar problem was observed

RE: Memory leak problem reported with gfortran

2008-02-03 Thread Dave Korn
On 03 February 2008 19:24, Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 Those of you most familiar with the Windows environment could perhaps help here. Is this a bug in Cygwin memory management? Are

Re: Memory leak problem reported with gfortran

2008-02-03 Thread Jerry DeLisle
Dave Korn wrote: On 03 February 2008 19:24, Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 Those of you most familiar with the Windows environment could perhaps help here. Is this a bug in Cygwin memory

Re: Memory leak problem reported with gfortran

2008-02-03 Thread Angelo Graziosi
Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 I do not know if this can help, but... Building the above test with G95, it does not fail! If I have understood it, I have pressed 1 ENTER without problem! With

Re: Memory leak problem reported with gfortran

2008-02-03 Thread Jerry DeLisle
Angelo Graziosi wrote: Jerry DeLisle wrote: I have confirmed this problem on Cygwin reported here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 I do not know if this can help, but... Building the above test with G95, it does not fail! If I have understood it, I have pressed 1