public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001124] Cortex M - stack corruption
Date: Fri, 21 Jan 2011 10:49:00 -0000 [thread overview]
Message-ID: <20110121104851.7E3C92F80002@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001124-13@http.bugs.ecos.sourceware.org/>
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.
next prev parent reply other threads:[~2011-01-21 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 18:06 [Bug 1001124] New: " bugzilla-daemon
2011-01-20 18:09 ` [Bug 1001124] " bugzilla-daemon
2011-01-21 10:49 ` bugzilla-daemon [this message]
2011-01-21 11:09 ` bugzilla-daemon
2011-01-23 8:59 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-01-20 18:06 [Bug 1001124] New: " bugzilla-daemon
2011-01-20 18:09 ` [Bug 1001124] " bugzilla-daemon
2011-01-21 10:49 ` bugzilla-daemon
2011-01-21 11:09 ` bugzilla-daemon
2011-01-23 8:59 ` bugzilla-daemon
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=20110121104851.7E3C92F80002@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@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).