From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Stack error...
Date: Fri, 20 Jul 2001 10:12:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.20.0107201009560.2292-100000@washoe.ics.uci.edu> (raw)
In-Reply-To: <3B578586.E21365DE@redhat.com>
It seems to be working fine with the diag_printf instead of printf. At
least it has been run for several hours already without any crash.
Thanks,
Cristiano.
> > 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?
>
> printf() does kernel operations like lock mutexes and so on. If used from
> _within_ the kernel I could easily imagine it causing you to fill up your
> stack, due to effectively calling into itself again and again. Try
> diag_printf() from <cyg/infra/diag.h> if you don't mind it being somewhat
> simpler than standard printf().
prev parent reply other threads:[~2001-07-20 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 17:20 Cristiano Ligieri Pereira
2001-07-19 18:12 ` Jonathan Larmour
2001-07-20 10:12 ` Cristiano Ligieri Pereira [this message]
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.0107201009560.2292-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).