From: "Lukas Riezler" <lukas.riezler@gmx.net>
To: ecos-discuss@sourceware.org
Subject: [ECOS] eCos application crashes
Date: Mon, 03 Jun 2013 19:31:00 -0000 [thread overview]
Message-ID: <trinity-294de98e-52c8-412f-9386-9bb53fd6f4f8-1370287875805@3capp-gmx-bs56> (raw)
Hi eCos-guys!
I have a problem with my fm3 port.
When I start an eCos application first it seems to run fine...but after ~1 second it crashes and restarts.
Do you have any idea what could be the reason for this behaviour?
I've tried to compile eCos without optimization ==> the first running was okay! The application did run fine!!!
But when I started it a few minutes later it crashed again...
I'll become desperate :/
With kind regards, Lukas
--
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 reply other threads:[~2013-06-03 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 19:31 Lukas Riezler [this message]
2013-06-03 19:49 ` Ilija Kocho
2013-06-03 20:14 ` Aw: " Lukas Riezler
2013-06-03 22:09 ` Ilija Kocho
2013-06-03 23:35 ` Aw: " Lukas Riezler
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=trinity-294de98e-52c8-412f-9386-9bb53fd6f4f8-1370287875805@3capp-gmx-bs56 \
--to=lukas.riezler@gmx.net \
--cc=ecos-discuss@sourceware.org \
/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).