From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9504 invoked by alias); 11 Oct 2013 09:16:07 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 9492 invoked by uid 89); 11 Oct 2013 09:16:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_20,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: illusory.impropriety.org.uk Received: from illusory.impropriety.org.uk (HELO illusory.impropriety.org.uk) (85.119.82.153) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 11 Oct 2013 09:16:05 +0000 Received: from 2.240.69.111.dynamic.snap.net.nz ([111.69.240.2] helo=[172.20.45.26]) by illusory.impropriety.org.uk with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1VUYpF-0003Vp-5H for ecos-discuss@ecos.sourceware.org; Fri, 11 Oct 2013 09:16:01 +0000 Message-ID: <5257C1CB.9000002@impropriety.org.uk> Date: Fri, 11 Oct 2013 09:16:00 -0000 From: Ross Younger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org References: <1380531306664-245720.post@n7.nabble.com> <1381479524136-247044.post@n7.nabble.com> In-Reply-To: <1381479524136-247044.post@n7.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-illusory-Ham-score: -1.0 X-illusory-Ham-score_int: -9 X-IsSubscribed: yes Subject: Re: [ECOS] Re: CyaSSL library port (WIP): Space for struct corrupts other eCos-data in RAM X-SW-Source: 2013-10/txt/msg00005.txt.bz2 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