http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54749
--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-09-29 17:34:04 UTC --- (In reply to comment #1) > You filed this against the "go" component, but it seems that Go is not > involved. Is that right? This is just about a backtrace printed after a run > of the Fortran compiler? yes, unclear what the proper component was for libbacktrace... I didn't consider this middle end either (and I was under the impression that go and libbracktrace had something in common). The problem is not the fact that this particular run crashes, but the fact that the trace should deal with the mmap out-of-mem more nicel (i.e. one line of error).
