From: Ralf Baechle <ralf@oss.sgi.com>
To: kjlin <kj.lin@viditec-netmedia.com.tw>
Cc: linux-mips@oss.sgi.com
Subject: Re: weird printf problem
Date: Sat, 21 Jul 2001 03:41:40 +0200 [thread overview]
Message-ID: <20010721034140.C22637@bacchus.dhis.org> (raw)
In-Reply-To: <016701c110c6$a371d580$056aaac0@kjlin>; from kj.lin@viditec-netmedia.com.tw on Fri, Jul 20, 2001 at 10:49:45AM +0800
On Fri, Jul 20, 2001 at 10:49:45AM +0800, kjlin wrote:
> Why too much "printf" will cause the program to die?
> Is it the problem of uClibc or kernel?
> Does the compiler for my testing program concern this weird problem?
> Can anybody give me some hints?
You gave no details such as sw version numbers and hardware details. However
given such random behaviour my guess would be a kernel bug, possibly the TLB
or cache managment code doesn't handle your CPU right.
Ralf
next prev parent reply other threads:[~2001-07-21 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 2:49 weird printf problem kjlin
2001-07-20 2:49 ` kjlin
2001-07-21 1:41 ` Ralf Baechle [this message]
2001-07-24 2:23 ` kjlin
2001-07-24 2:23 ` kjlin
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=20010721034140.C22637@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=kj.lin@viditec-netmedia.com.tw \
--cc=linux-mips@oss.sgi.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