From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Stack error...
Date: Thu, 19 Jul 2001 17:20:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.20.0107191716290.373-100000@washoe.ics.uci.edu> (raw)
I consistently getting this error in my application after it's running for
a while:
ASSERT FAIL: <4>[102]void Cyg_HardwareThread::check_stack() Stack base
corrupt
How could I corrupt the base of my stack?
I'm using some debugging printf's within the kernel instead of TRACING
cause the TRACING messages are too big... Could it be a possible problem?
Thanks,
Cristiano.
PS: I'm running it using Linux-synthetic
------------------------------------------------------------
Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira
next reply other threads:[~2001-07-19 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 17:20 Cristiano Ligieri Pereira [this message]
2001-07-19 18:12 ` Jonathan Larmour
2001-07-20 10:12 ` Cristiano Ligieri Pereira
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=Pine.SOL.4.20.0107191716290.373-100000@washoe.ics.uci.edu \
--to=cpereira@ics.uci.edu \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).