From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4687 invoked by alias); 6 May 2005 20:12:28 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 4538 invoked from network); 6 May 2005 20:12:19 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org with SMTP; 6 May 2005 20:12:19 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1DU9B9-0003HX-00; Fri, 06 May 2005 22:12:07 +0200 Date: Fri, 06 May 2005 20:46:00 -0000 To: David Brennan Cc: eCos Discussion List Message-ID: <20050506201207.GJ31731@lunn.ch> Mail-Followup-To: David Brennan , eCos Discussion List References: <427B77BF.5010302@brennanhome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427B77BF.5010302@brennanhome.com> User-Agent: Mutt/1.5.9i From: Andrew Lunn Subject: Re: [ECOS] Memory allocation failure X-SW-Source: 2005-05/txt/msg00092.txt.bz2 On Fri, May 06, 2005 at 06:57:19AM -0700, David Brennan wrote: > I have created two different applications with the same eCos > configuration and essentially the same code base. One trivial > application which is missing most of the meat of the main application. > The trivial application runs fine. However when I try and start the real > application, it dies during my static constructors. I have traced the > problem down to a malloc call, but GDB eventually hangs while trying to > single step through there. It always hangs at this one particular > malloc, when constructing one particular instantiation of a class. Any > ideas? Is there a fixed number of pool elements which can be allocated > using dlmalloc? > Target is i386 VME based PC. A total guess..... You say this is a constructor. When is the constructor called? Is it a static constructor which will be called early during startup? Have you checked that malloc's constructor has already been called so that malloc itself is read to be called? Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss