public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: David Brennan <eCos@brennanhome.com>
Cc: eCos Discussion List <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Memory allocation failure
Date: Fri, 06 May 2005 20:46:00 -0000	[thread overview]
Message-ID: <20050506201207.GJ31731@lunn.ch> (raw)
In-Reply-To: <427B77BF.5010302@brennanhome.com>

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

  reply	other threads:[~2005-05-06 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 13:57 David Brennan
2005-05-06 20:46 ` Andrew Lunn [this message]
2005-05-07  7:54   ` David Brennan
2005-05-09  8:16     ` Andrew Lunn
2005-05-10 10:03       ` David Brennan
2005-05-07 16:19 ` Edgar Grimberg

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=20050506201207.GJ31731@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=eCos@brennanhome.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).