From: Daniel Zebralla <daniel.zebralla@zebralla-it.de>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: CyaSSL library port (WIP): Space for struct corrupts other eCos-data in RAM
Date: Fri, 11 Oct 2013 08:18:00 -0000 [thread overview]
Message-ID: <1381479524136-247044.post@n7.nabble.com> (raw)
In-Reply-To: <1380531306664-245720.post@n7.nabble.com>
I now solved the problem by putting all CyaSSL-related stuff and tests into
an individual thread:
void create_TLS_thread(void)
{
cyg_mutex_init(&cliblock_TLS);
cyg_thread_create(
TLS_THREAD_PRIOTITY,
TLS_communication,
(cyg_addrword_t) 1,
"TLS Communication",
(void *) tls_stack,
sizeof(tls_stack),
&TLS_Thread,
&thread_tls
);
cyg_thread_resume(TLS_Thread);
printf("TLS-Thread created!\n");
}
Suddenly, all tests complete successfully and no memory is corrupted.
Is there some general rule of thumb, that one should not do memory-intensive
work in the 'main'-thread?
Regards
- Daniel
--
View this message in context: http://sourceware-org.1504.n7.nabble.com/CyaSSL-library-port-WIP-Space-for-struct-corrupts-other-eCos-data-in-RAM-tp245720p247044.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
--
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 8:18 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 ` Daniel Zebralla [this message]
2013-10-11 9:16 ` [ECOS] " Ross Younger
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=1381479524136-247044.post@n7.nabble.com \
--to=daniel.zebralla@zebralla-it.de \
--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).