From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20080 invoked by alias); 25 Apr 2008 16:48:20 -0000 Received: (qmail 20045 invoked by uid 22791); 25 Apr 2008 16:48:18 -0000 X-Spam-Check-By: sourceware.org Received: from lola.electric.net (HELO lola.electric.net) (72.35.23.29) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Apr 2008 16:47:50 +0000 Received: from 1JpR5N-0000h8-UI by lola.electric.net with emc1-ok (Exim 4.67) (envelope-from ) id 1JpR5O-0000iW-Vr; Fri, 25 Apr 2008 09:47:46 -0700 Received: by emcmailer; Fri, 25 Apr 2008 09:47:46 -0700 Received: from [81.133.194.167] (helo=[192.168.113.64]) by lola.electric.net with esmtpa (Exim 4.67) (envelope-from ) id 1JpR5N-0000h8-UI; Fri, 25 Apr 2008 09:47:45 -0700 Message-ID: <48120B2D.5060008@ad-holdings.co.uk> Date: Sat, 26 Apr 2008 00:19:00 -0000 From: Dave Lawrence User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 Newsgroups: gmane.os.ecos.general To: "Davies, Greg" CC: ecos discuss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Outbound-IP: 81.133.194.167 X-Env-From: dlawrence@ad-holdings.co.uk X-Virus-Status: Scanned by VirusSMART (c) 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 Subject: [ECOS] Re: System failure!! X-SW-Source: 2008-04/txt/msg00210.txt.bz2 Message-ID: <20080426001900.vMmjPt_rm717R7uBCAlmaGss7anUvmYqZ7kEaakmyqM@z> Davies, Greg wrote: > > -----Original Message----- >> Alperen Coskun >> Sent: Thursday, April 24, 2008 11:30 AM >> >> There is no compilation error. But when I download xxx.elf >> file that I generated, my program stops at one of the >> functions. (In fact it doesn't stop, it enters a loop in >> cyg_hal_default_exception_vsr at different places in asm code >> but generally in"sync" assembly code. It doesn't break the > > This reminds me of a problem I had a little while ago. The symptoms > aren't the same but the inconsistency of the symptoms is. The fact that > you say eCos was working by chance sounds similar to my issue too. I > never actually solved it or found out what was wrong, but I made it go > away by doing a thorough cleaning of the entire project, including the > generated eCos source tree. I've found there's configuration things that > can get left over sometimes, and will let you keep compiling, even if > the configuration is no good for building from scratch. It's something > quick to try anyway. > Yes there's definately problems with this. Using the graphical tool, the tree is always regenerated if you use the tool to modify the config, but if something else modifies the ecc (eg your version control system brings in someone else's changes) then these changes might not get incorporated in your build. I don't know if your using configtool or ecosconfig, but now we use both. configtool to edit the ecc, and ecosconfig --tree at the beginning of the build script (disregarding the tree generated by configtool). The other two issues I've seen: - Changing global build flags doesn't cause a rebuild of everything, as you might expect. Although I have found you can take advantage of this bug to individually switch off optimisation or enable instrumentation on certain files. - Where include files are added or removed, the built tree must be deleted and regenerated. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss