From: Michael Bergandi <mbergandi@gmail.com>
To: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Set stack size for main
Date: Thu, 10 Mar 2011 19:47:00 -0000 [thread overview]
Message-ID: <AANLkTi=t1LC19xMbXugVx+dGz2h5fN+rw43jqn53Pd7H@mail.gmail.com> (raw)
Hi all,
I have a test app that seems to crash in random locations. After
probing with gdb for a bit, it appears that an interupt occurs at some
point and then the app crashes with:
ASSERT FAIL: <3240>sched.cxx[160]static void
Cyg_Scheduler::unlock_inner() Bad current thread
I am thinking that this is probably a corrupt stack problem, but I am
not sure how to know for sure. Assuming it is a stack problem and it
is just too small, can someone explain how I can set/check the stack
size of main()?
Thanks,
--
Mike
next reply other threads:[~2011-03-10 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 19:47 Michael Bergandi [this message]
2011-03-10 19:56 ` Gary Thomas
2011-03-14 14:59 ` Michael Bergandi
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='AANLkTi=t1LC19xMbXugVx+dGz2h5fN+rw43jqn53Pd7H@mail.gmail.com' \
--to=mbergandi@gmail.com \
--cc=ecos-devel@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).