[Bug fortran/85840] Memory leak in write.c

2018-06-01 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 Jerry DeLisle changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/85840] Memory leak in write.c

2018-06-01 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #16 from Jerry DeLisle --- Author: jvdelisle Date: Fri Jun 1 18:34:09 2018 New Revision: 261077 URL: https://gcc.gnu.org/viewcvs?rev=261077&root=gcc&view=rev Log: 2018-06-01 Jerry DeLisle Backport from trunk. PR

[Bug fortran/85840] Memory leak in write.c

2018-05-31 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #15 from Jerry DeLisle --- Author: jvdelisle Date: Fri Jun 1 02:14:53 2018 New Revision: 261054 URL: https://gcc.gnu.org/viewcvs?rev=261054&root=gcc&view=rev Log: 2018-05-31 Jerry DeLisle Backport from trunk. PR

[Bug fortran/85840] Memory leak in write.c

2018-05-28 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #14 from Jerry DeLisle --- Author: jvdelisle Date: Mon May 28 21:55:31 2018 New Revision: 260851 URL: https://gcc.gnu.org/viewcvs?rev=260851&root=gcc&view=rev Log: 2018-05-28 Jerry DeLisle PR libgfortran/85840 * i

[Bug fortran/85840] Memory leak in write.c

2018-05-26 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #13 from Jerry DeLisle --- Author: jvdelisle Date: Sun May 27 03:22:11 2018 New Revision: 260802 URL: https://gcc.gnu.org/viewcvs?rev=260802&root=gcc&view=rev Log: 2018-05-26 Jerry DeLisle Backport from trunk. PR

[Bug fortran/85840] Memory leak in write.c

2018-05-26 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #12 from Jerry DeLisle --- Fixed on trunk. I think this should be backported as it is a regression I think on 7 and 8 branches.

[Bug fortran/85840] Memory leak in write.c

2018-05-26 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #11 from Jerry DeLisle --- Author: jvdelisle Date: Sat May 26 17:30:52 2018 New Revision: 260793 URL: https://gcc.gnu.org/viewcvs?rev=260793&root=gcc&view=rev Log: 2018-05-26 Jerry DeLisle PR libgfortran/85840 * i

[Bug fortran/85840] Memory leak in write.c

2018-05-26 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #10 from Jerry DeLisle --- (In reply to Joshua Cogliati from comment #9) --- snip --- > I could look into either method of fixing this if you want. (And for what > it is worth, I do have copyright assignment paperwork from both mysel

[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #9 from Joshua Cogliati --- Looking at write.c, there are multiple places where things like the pattern: result = select_string (dtp, f, str_buf, &res_len, kind); ... get_float_string (dtp, f, source , kind, 0, buffer,

[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #8 from Joshua Cogliati --- Created attachment 44186 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44186&action=edit Patch by keeping original length This patches the problem by storing the allocated length in a separate varia

[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #7 from Joshua Cogliati --- Created attachment 44185 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44185&action=edit Patch by checking against original buffer This is one possible patch for this problem, it just checks if the

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 Jerry DeLisle changed: What|Removed |Added Status|WAITING |ASSIGNED Assignee|unassigned a

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #5 from Jerry DeLisle --- I will see if I can reproduce this here with you example and if so will get on it.

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #4 from Joshua Cogliati --- And to replicate it with the simple program: gfortran -Wall -g -o simple simple.f90 valgrind --leak-check=full ./simple and you get things like: ==19171== 323 bytes in 1 blocks are definitely lost in

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #3 from Joshua Cogliati --- Created attachment 44150 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44150&action=edit simple program to demonstrate problem

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 Joshua Cogliati changed: What|Removed |Added CC||jjcogliati-r1 at yahoo dot com --- Com

[Bug fortran/85840] Memory leak in write.c

2018-05-19 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|