public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Ottawa Guy <ottawaguy81@yahoo.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] static class initilization order
Date: Thu, 23 Oct 2003 14:30:00 -0000	[thread overview]
Message-ID: <m33cdk2fhp.fsf@miso.calivar.com> (raw)
In-Reply-To: <20031023035520.57734.qmail@web13004.mail.yahoo.com>

Ottawa Guy <ottawaguy81@yahoo.com> writes:

> Hi,
> I am trying to use malloc function from malloc.cxx
> file. Inside that file cyg_memalloc_mallocpool class
> gets initilized and there is an initialization
> condition on this class.
> 
> Is there any gcc any flag I need to set to keep the
> proper initilization order.
> 
> 
> Right now when ever I use malloc in my code, my
> simulator just crashes, even though I am not making
> the actual "malloc" call. I figured this is  something
> to do  with my constructor.

If you are using a simulator then you can presumably just break in and
see what the program is doing. You should also be able to put a
breakpoint on the constructor and step through it to see where it is
failing. 

What platform are you configuring for, and what simulator? Bear in
mind that the GDB simulator for most architectures is really there for
compiler development only, it cannot fully emulate the hardware of a
real board.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-10-23 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23  3:55 Ottawa Guy
2003-10-23 14:30 ` Nick Garnett [this message]

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=m33cdk2fhp.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=ottawaguy81@yahoo.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).