From: Nick Garnett <nickg@ecoscentric.com>
To: Rycerz Roman-G11565 <roman.rycerz@motorola.com>
Cc: "Ecos-Discuss@Sources. Com (ecos-discuss@sources.redhat.com)"
<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] HAL startup help.
Date: Mon, 02 Aug 2004 10:07:00 -0000 [thread overview]
Message-ID: <m3y8kxam5z.fsf@xl5.calivar.com> (raw)
In-Reply-To: <5D454811D0A1D711A12A00065BF36FAD08B9E034@il06exm11>
Rycerz Roman-G11565 <roman.rycerz@motorola.com> writes:
> I am hoping someone can help me. I have a rather strange problem that comes and goes for reasons that so far escape me.
> While I am not sure what makes this situation appear and disappear, maybe this behavior will ring some bells.
>
>
> When the ecos world is happy, the routine "cyg_hal_invoke_constructors" executes, behaves nicely and executes a list of constructors.
> such as
> Global_I10100_diag_write_char
> Global_I11000_cyg_scheduler_sched_lock
> Global_I12000_ZB13cyg_Interrupt15....
>
>
> When ecos is unhappy "cyg_hal_invoke_constructors" actually executes a list of destructors
>
> Global_D14000......
> Global_D15000.......
>
>
> Anyone know what might cause this ???? I am sure its something I am doing, but so far I have no clue....
Cannot help you specifically, but in the past when I have seen things
like this happening, it has often been an alignment issue. It appears
and disappears as changing sizes of text and data change the alignment
of later data items.
Check that the alignment requirements in your linker script are
correct. If you try single stepping through
cyg_hal_invoke_constructors() when it is misbehaving you should be
able to work out what is going wrong.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-08-02 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 20:11 Rycerz Roman-G11565
2004-08-02 10:07 ` Nick Garnett [this message]
2004-08-06 16:36 Rycerz Roman-G11565
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=m3y8kxam5z.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=roman.rycerz@motorola.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).