From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Debugging Infinite Loop
Date: Wed, 23 Mar 2011 04:05:56 +0700 [thread overview]
Message-ID: <AANLkTi=uZk5eNFMRDwUEbNdhpPeyz0-XExzCxT8r_B7e@mail.gmail.com> (raw)
In-Reply-To: <AANLkTins3PGjWG1SmcGsbo3kuOW0gcgpv_HMp-BwQNe8@mail.gmail.com>
On Wed, Mar 23, 2011 at 03:49, Dev Null <devnullfin@gmail.com> wrote:
> Hi,
>
> I have an infinite loop in my huge application/kernel module i.e. either in
> kernel or application that boost up CPU utilization to 100%. I have an
> application that reads multicast UDP packet, process it and send it to the
> peripheral device on PCI interface.
my guess: either you don't yield yourself at certain amount of data,
or you simply forgot to enable the interrupt again when you previously
disable it... thus disallowing practically anything to interrupt your
way...
> I need to know the best approach or tool to debug the infinite loop.
maybe oprofile...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-03-22 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 20:49 Debugging Infinite Loop Dev Null
2011-03-22 21:05 ` Mulyadi Santosa [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='AANLkTi=uZk5eNFMRDwUEbNdhpPeyz0-XExzCxT8r_B7e@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).