This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/61831] [4.9/ 5 Regression] runtime error: pointer being freed was not allocated
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 14 Feb 2015 10:16:02 +0000
- Subject: [Bug fortran/61831] [4.9/ 5 Regression] runtime error: pointer being freed was not allocated
- Auto-submitted: auto-generated
- References: <bug-61831-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61831
--- Comment #37 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > [...]
> > if (D.3430.chars.data != 0B)
> > {
> > __builtin_free ((void *) D.3430.chars.data);
> > }
> > D.3430.chars.data = 0B;
>
> D.3430.chars.data is freed.
>
> So every iteration of the do loop has the side-effect of freeing prt_in.chars.data.
Could you please give me a pointer to the code emitting this side-effect?