This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001124] Cortex M - stack corruption


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 <nickg@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickg@ecoscentric.com

--- Comment #2 from Nick Garnett <nickg@ecoscentric.com> 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 on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]