Bug 14456 - internal-error: virtual memory exhausted
Summary: internal-error: virtual memory exhausted
Status: WAITING
Alias: None
Product: gdb
Classification: Unclassified
Component: c++ (show other bugs)
Version: 7.4
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-11 16:03 UTC by Tomas
Modified: 2014-11-17 23:14 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas 2012-08-11 16:03:27 UTC
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;
}
Comment 1 Keith Seitz 2012-08-14 17:07:18 UTC
I tried to reproduce this but failed on both 7.4.1-20120718-cvs and 7.5.50-20120808-cvs (HEAD from one week ago).

Does the problem occur if you disable pretty-printing of STL containers?

I don't suppose you could reproduce the error and provide a stack backtrace? That would be incredibly useful.
Comment 2 dje 2014-11-17 23:14:28 UTC
Perhaps related, perhaps not, but fyi,
see pr 17614 for an OOM with a backtrace.