https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
--- Comment #7 from GCC Commits ---
The releases/gcc-14 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:ca652aebd30132b2a9afbc07c664a35b5e443350
commit r14-11276-gca652aebd30132b2a9afbc07c664a35b5e443350
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
anlauf at gcc dot gnu.org changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
--- Comment #5 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:d6418fe22684f9335474d1fd405ade45954c069d
commit r15-7308-gd6418fe22684f9335474d1fd405ade45954c069d
Author: Harald Anlauf
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 60322
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60322&action=edit
Patch part 1
This fixes the memory corruption due to false freeing of the
symbol during resolution.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
--- Comment #2 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> The code crashing gfortran may actually be valid.
I set a breakpoint in parse.cc:7386
Breakpoint 1, gfc_parse_file () at ../../gcc-trunk/gcc/fortran/parse.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108454
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-01-18
Statu
