From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9651 invoked by alias); 21 Jan 2011 10:49:09 -0000 Received: (qmail 9639 invoked by uid 22791); 21 Jan 2011 10:49:09 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 21 Jan 2011 10:48:55 +0000 Received: by mail.ecoscentric.com (Postfix, from userid 48) id D4D542F78001; Fri, 21 Jan 2011 10:48:52 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001124] Cortex M - stack corruption X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: HAL X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nickg@ecoscentric.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 21 Jan 2011 10:49:00 -0000 Message-Id: <20110121104851.634B12F80001@mail.ecoscentric.com> Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2011/txt/msg00168.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001124 Nick Garnett changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nickg@ecoscentric.com --- Comment #2 from Nick Garnett 2011-01-21 10:48:48 GMT --- Christophe, This is not right. It would leave the interrupt stack pointing to halfway through the stack area. Since the interrupt stack is usually placed in on-chip SRAM, this wastes some precious memory. I am also not sure how you get any interrupts before the first context switch moves to a real thread stack. The context switch code changes stack before setting BASEPRI, which is when the first interrupt may occur. You should not be getting any interrupts or exceptions before this point, if you are then I suspect you have accidentally enabled interrupts in some piece of initialization code. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.