From: Gary Thomas <gary@mlbassoc.com>
To: Rycerz Roman-G11565 <roman.rycerz@motorola.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Startup problem
Date: Thu, 10 Jun 2004 16:01:00 -0000 [thread overview]
Message-ID: <1086883267.3643.1780.camel@hermes> (raw)
In-Reply-To: <5D454811D0A1D711A12A00065BF36FAD08B9DF30@il06exm11>
On Thu, 2004-06-10 at 09:49, Rycerz Roman-G11565 wrote:
> Sorry I keep forgetting to include the environments
>
> * What target platform [processor architecture] -> Power PC on a MPC5554
> * What tools are you using -> gcc 2.95.3-10, Insight 5.2, ecos config tool 2.11
> * What eCos configuration -> I/O subsystem, Serial Device Drivers, eCos Kernel
> * Is this repeatable or random -> random in the sense that from 1 compile to the next it comes and goes
>
What about rerunning the same binary? If it fails, does it always fail,
or only sometimes? If it's the latter, I'd suspect a RAM problem.
If it always fails, then it may be a compiler issue.
>
> Roman
>
>
>
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Sent: Thursday, June 10, 2004 10:33 AM
> To: Sven Rehfuss
> Cc: Rycerz Roman-G11565; ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] Startup problem
>
>
> On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> > Hi,
> > use a debugger and check the code. If the routines modify stack
> > variables before decrementing the stack pointer, it maybe is the same
> > problem I had. If it is the same problem, I can give you the solution.
>
> Why not share this solution with us all? After all, that's what this forum is for!
>
> >
> > Regards,
> > Sven Rehfu?
> >
> >
> > Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > > Hi
> > >
> > > I have an intermittent problem. When starting up the eCos kernel
> > > the call to "cyg_hal_invoke_constructors" sometimes fails with a
> > > segmentation violation. It seems to happening when the destructors
> > > are being called. in thread.cxx
> > >
> > > its in the routine "~cyg_thread_remove_from_list", it seem to be
> > > working it way back thru a linked list assigning
> > > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location a null ptr problem.
> > >
> > > I know this is a quite vague description, and I may all wrong.. But
> > > does anyone have any ideas why this is happening ???
>
> You've not told us much about your environment.
> * What target platform [processor architecture]?
> * What tools are you using
> * What eCos configuration
> * Is this repeatable or random
>
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
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-06-10 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 15:49 Rycerz Roman-G11565
2004-06-10 16:01 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 18:28 Rycerz Roman-G11565
2004-06-10 15:08 Rycerz Roman-G11565
2004-06-10 15:22 ` Sven Rehfuss
2004-06-10 15:33 ` Gary Thomas
2004-06-10 15:39 ` Sven Rehfuss
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=1086883267.3643.1780.camel@hermes \
--to=gary@mlbassoc.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).