public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67414] [5 Regression] Error message on failed allocate
Date: Mon, 31 Aug 2015 21:03:00 -0000	[thread overview]
Message-ID: <bug-67414-4-GTVD61mg1A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67414-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67414

Janne Blomqvist <jb at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-08-31
                 CC|                            |fxcoudert at gcc dot gnu.org,
                   |                            |jb at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Janne Blomqvist <jb at gcc dot gnu.org> ---
Confirmed.

I'd say this is a WONTFIX. The reason is that with the new libbacktrace-based
backtrace code the backtrace is generated in the same process, whereas the old
implementation forked a copy of addr2line which did the symbol lookup. So when
the code fails due to bumping into the memory limit, generating the backtrace
fails. However, as there are several benefits of the new libbacktrace way, I
don't think we want to go back to the old addr2line way.

That being said, I have a patch which 1) Improves the error message for
backtracing failing 2) Fixes the root case for the segfault here. Fixing issue
2) actually makes the backtrace go away, so uh.. Well, that's more an issue for
PR 53379 anyway.


  reply	other threads:[~2015-08-31 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 16:32 [Bug fortran/67414] New: " Joost.VandeVondele at mat dot ethz.ch
2015-08-31 21:03 ` jb at gcc dot gnu.org [this message]
2015-09-01  8:34 ` [Bug fortran/67414] [5/6 " rguenth at gcc dot gnu.org
2015-09-02 14:52 ` jb at gcc dot gnu.org
2015-09-02 15:16 ` jb at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-67414-4-GTVD61mg1A@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).