From: Ross Younger <ecos@impropriety.org.uk>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: CyaSSL library port (WIP): Space for struct corrupts other eCos-data in RAM
Date: Fri, 11 Oct 2013 09:16:00 -0000 [thread overview]
Message-ID: <5257C1CB.9000002@impropriety.org.uk> (raw)
In-Reply-To: <1381479524136-247044.post@n7.nabble.com>
On 11/10/13 21:18, Daniel Zebralla wrote:
> I now solved the problem by putting all CyaSSL-related stuff and tests into
> an individual thread:
> Is there some general rule of thumb, that one should not do
memory-intensive
> work in the 'main'-thread?
Did you by any chance put your RsaKey struct on the stack, as opposed to
static or malloced? Threads in eCos often have very small stacks; the
corruption you describe sounds typical of a stack overrun.
You can find the stack size for the default ("main") thread in the .ecc
file you're using.
Ross
--
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:[~2013-10-11 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 8:55 [ECOS] " Daniel Zebralla
2013-10-11 8:18 ` [ECOS] " Daniel Zebralla
2013-10-11 9:16 ` Ross Younger [this message]
2013-10-14 7:59 ` Daniel Zebralla
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=5257C1CB.9000002@impropriety.org.uk \
--to=ecos@impropriety.org.uk \
--cc=ecos-discuss@ecos.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).