From: "jay_chen" <jay_chen@alphanetworks.com>
To: "'Nicholas Mc Guire'" <hofrat@hofr.at>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Kernel stack overflow in process xxxx
Date: Wed, 19 Mar 2008 20:59:49 +0800 [thread overview]
Message-ID: <038001c889c1$205d7bb0$016ffea9@alphajay> (raw)
In-Reply-To: <Pine.LNX.4.58.0803180908270.1963@vlab.hofr.at>
Hi,
My kernel version is 2.6.14.5
I don't see these options.
Jay...
-----Original Message-----
From: Nicholas Mc Guire [mailto:hofrat@hofr.at]
Sent: Wednesday, March 19, 2008 2:13 AM
To: jay_chen
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Kernel stack overflow in process xxxx
> By the way, is there any skill/tool to avoid/detect/check this kind of
> problem?
>
did you try:
Kernel hacking --->
...
[*] Kernel debugging
...
[*] Check for stack overflows
[*] Stack utilization instrumentation
the last one depends on SysRq though.
In any case it would be interesting to know if these tools can help find
problems of this kind - so if it does not help - pleas let me/us know.
hofrat
prev parent reply other threads:[~2008-03-19 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 7:12 Kernel stack overflow in process xxxx jay_chen
2008-03-17 7:17 ` jay_chen
2008-03-18 18:12 ` Nicholas Mc Guire
2008-03-19 12:59 ` jay_chen [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='038001c889c1$205d7bb0$016ffea9@alphajay' \
--to=jay_chen@alphanetworks.com \
--cc=hofrat@hofr.at \
--cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).