public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/67457] segfault in libbacktrace
Date: Tue, 08 Sep 2015 17:16:00 -0000	[thread overview]
Message-ID: <bug-67457-4-sCtRlerZNB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67457-4@http.gcc.gnu.org/bugzilla/>

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


  parent reply	other threads:[~2015-09-08 17:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05  7:22 [Bug other/67457] New: " Joost.VandeVondele at mat dot ethz.ch
2015-09-08 13:49 ` [Bug other/67457] " ian at gcc dot gnu.org
2015-09-08 14:06 ` ian at airs dot com
2015-09-08 14:50 ` Joost.VandeVondele at mat dot ethz.ch
2015-09-08 16:46 ` ian at airs dot com
2015-09-08 16:46 ` ian at gcc dot gnu.org
2015-09-08 17:16 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2021-08-24 18:58 ` pinskia 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-67457-4-sCtRlerZNB@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).