From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25145 invoked by alias); 19 May 2003 17:02:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25121 invoked from network); 19 May 2003 17:02:12 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 19 May 2003 17:02:12 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19Ho24-0004Ch-00; Mon, 19 May 2003 12:02:40 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19Ho1W-0001Su-00; Mon, 19 May 2003 13:02:06 -0400 Date: Mon, 19 May 2003 17:02:00 -0000 From: Daniel Jacobowitz To: Andreas =?iso-8859-1?Q?Gro=DF?= Cc: gdb@sources.redhat.com Subject: Re: Virtual memory Message-ID: <20030519170206.GA5616@nevyn.them.org> Mail-Followup-To: Andreas =?iso-8859-1?Q?Gro=DF?= , gdb@sources.redhat.com References: <200305191557.20097.gross_andreas@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200305191557.20097.gross_andreas@web.de> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00271.txt.bz2 On Mon, May 19, 2003 at 03:57:19PM +0000, Andreas Groß wrote: > Hi there... > > I'm programming a patch for gdb which gives out a state graph of a program. I > have the following problem: > I store the state graph in the heap memory (using xmalloc). The problem is > that I get an out-of-memory-error while computing the state graph of huge > programs: > > utils.c:981: gdb-internal-error: virtual memory exhausted: can't allocate > 49220 bytes. > An internal GDB error was detected. This may make further > debugging unreliable. Quit this debugging session? (y or n) y > > My question: Is it possible to say gdb to allocate more virtual memory? If you get that error, then you've really run out of memory, as reported by your operating system; there's not much to be done about it. How big is this state graph anyway? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer