From: Sven Rehfuss <sven.rehfuss@b2motion.de>
To: Rycerz Roman-G11565 <roman.rycerz@motorola.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Startup problem
Date: Thu, 10 Jun 2004 15:22:00 -0000 [thread overview]
Message-ID: <1086881010.2454.412.camel@linux.local> (raw)
In-Reply-To: <5D454811D0A1D711A12A00065BF36FAD08B9DF2E@il06exm11>
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.
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 ???
>
> thanks
> roman
>
--
B2motion GmbH
Sven Rehfuß
Projekt/System Engineer
Otto-Lilienthal Straße 29
D-28199 Bremen
Tel.: +49 421 24111 - 22
Fax : +49 421 24111 - 99
Mobil: +49 179 7058740
Email: sven.rehfuss@b2motion.de
--
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 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 15:08 Rycerz Roman-G11565
2004-06-10 15:22 ` Sven Rehfuss [this message]
2004-06-10 15:33 ` Gary Thomas
2004-06-10 15:39 ` Sven Rehfuss
2004-06-10 15:49 Rycerz Roman-G11565
2004-06-10 16:01 ` Gary Thomas
2004-06-10 18:28 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=1086881010.2454.412.camel@linux.local \
--to=sven.rehfuss@b2motion.de \
--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).