https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
Robert Dubner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #8 from Simon Sobisch ---
Hm, sounds like an internal stack check or similar would be good here to
circumvent this issue from another side...
If it doesn't work then it would definitely better for gcc to abort compiling
this code fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #7 from Robert Dubner ---
The DB programs are not among the ones we test.
When I run the program, it rapidly gets stuck in an infinite loop around lines
511 513. It just keeps attempting to PERFORM DEBUG-ALL-PROCS, repeatedly. So,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #6 from Simon Sobisch ---
I wanted to originally say that's fixed (the memory leak in EXEC85 is), but
running NIST DB105A still produces the same issue.
heaptrack shows 34,4GB leaked, most allocations (256+63) come from allocate in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #5 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:29ac3adb8f72ecbe734d535b1015fe8b411316cb
commit r15-9156-g29ac3adb8f72ecbe734d535b1015fe8b411316cb
Author: Bob Dubner
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #4 from Simon Sobisch ---
Am 28. März 2025 15:40:49 GMT-12:00 schrieb "rdubner at gcc dot gnu.org"
:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
>
>--- Comment #2 from Robert Dubner ---
>Additional: The leaking memory is b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #3 from Simon Sobisch ---
Note: some people will argue that the program should only abort, because/when
exception checking is on.
At least if it is, libgcobol needs to save the location, statement, file and
exception that happened (f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #2 from Robert Dubner ---
Additional: The leaking memory is because exception checking is turned on.
Still looking...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
Robert Dubner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
