public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001124] New: Cortex M - stack corruption Date: Thu, 20 Jan 2011 18:06:00 -0000 [thread overview] Message-ID: <bug-1001124-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001124 Summary: Cortex M - stack corruption Product: eCos Version: CVS Platform: All OS/Version: Cortex-M Status: UNCONFIRMED Severity: normal Priority: low Component: HAL AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: ecos@hotmail.co.uk CC: ecos-bugs@ecos.sourceware.org Class: Advice Request It is possible to corrupt the stack during the board initialisation when compiling a ROM application with the KERNEL package. The RTC clock is started from cyg_hal_invoke_constructors() and, at this point, the main stack pointer (MSP) and the thread stack pointer (PSP) are equal. In case the eCos scheduler has not switched the PSP to a thread stack before the first RTC interrupt happens, the stack get corrupted. This typically happens if you have some debugging diag_printf in some of the constructors. Christophe -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2011-01-20 18:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-20 18:06 bugzilla-daemon [this message] 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 -- strict thread matches above, loose matches on Subject: below -- 2011-01-20 18:06 [Bug 1001124] New: " 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=bug-1001124-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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: linkBe 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).