This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [gfortran] segfault at end of procedure when using deallocate


On Saturday 29 November 2003 7:44 am, Melvin Hadasht wrote:
> Note that if deallocate() is not used, the program does not show any
> error message and it does not segfault. It looks like double-freeing.
> Please, see my previous post
> [gfortran] bug: allocation of already allocated array does not fail
> (2003-11-29), maybe these two have a something in common.
>
> As of this writing, this is the current CVS (top ChangeLogs lists
> 2003-11-28  Richard Henderson  <rth@redhat.com>)
>
> I saw that last ChangeLog entries have something to do with array
> allocation, so I'm not sure if this is a bug due to CVS quick change
> or if it is a real bug that I would better report to bugzilla.

It was a bug, but has been fixed now.
It's not related to the double allocation bug.

Paul.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]