https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67457
--- Comment #6 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch>
---
(In reply to Ian Lance Taylor from comment #4)
> I committed a patch that should produce a more graceful fallback when out of
> memory. Please see if it helps your situation.
Great! Not sure how you managed, but this gives a clean symbolic backtrace, at
least for this simple test case:
> ./a.out
Operating system error: Cannot allocate memory
Allocation would exceed memory limit
Error termination. Backtrace:
Could not print backtrace: mmap: Cannot allocate memory
Could not print backtrace: mmap: Cannot allocate memory
Could not print backtrace: mmap: Cannot allocate memory
Could not print backtrace: mmap: Cannot allocate memory
Could not print backtrace: mmap: Cannot allocate memory
#0 0x7f068c128e09 in ???
#1 0x7f068c129905 in ???
#2 0x7f068c129b02 in ???
#3 0x40081d in __foomod_MOD_foo
at /data/vjoost/gnu/bugs/test_1.f90:7
#4 0x4008bf in MAIN__
at /data/vjoost/gnu/bugs/test_1.f90:16
#5 0x4008f5 in main
at /data/vjoost/gnu/bugs/test_1.f90:12
