public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "thamos at email dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/14456] New: internal-error: virtual memory exhausted
Date: Sat, 11 Aug 2012 16:03:00 -0000	[thread overview]
Message-ID: <bug-14456-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14456

             Bug #: 14456
           Summary: internal-error: virtual memory exhausted
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: thamos@email.cz
    Classification: Unclassified


GDB (with python support) crashes with following description:

C:/MinGW/msys/1.0/src/gdb/gdb-python-7.4-1-mingw32-src/gdb-python-7.4-2/src/gdb-7.4/gdb/utils.c:1246:
internal-error: virtual memory exhausted: can't allocate 2009222722 bytes.

when stepping into x constructor (main) in this C++ code:

#include <string>

class T
{
public:
    T(std::string str)
    {
    }
};


int main() {
    std::string str = "";
    T x(str);
    return 0;
}

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-08-11 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11 16:03 thamos at email dot cz [this message]
2012-08-14 17:07 ` [Bug c++/14456] " keiths at redhat dot com
2012-08-22 15:02 ` palves at redhat dot com
2014-11-17 23:14 ` dje at google dot com

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-14456-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).