From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Stupid question about the output of show_task()
Date: Sun, 11 May 2003 20:29:08 -0400 [thread overview]
Message-ID: <200305112032_MC3-1-386D-F200@compuserve.com> (raw)
I'm trying to decipher the output of alt-sysrq-t on i386 running
2.4.21-rc2-ac1:
free sibling
task PC stack pid father child younger older
init S 000001F0 4352 1 0 943 (NOTLB)
Why does it report the program counter as 0x1f0? This comes from
((unsigned long *)thread_struct.esp)[3], i.e. the third item from the
top of the saved process stack. Why do many of the processes show
completely invalid values for the instruction pointer? And where is
the layout for the stack of sleeping processes documented?
Some processes show large numbers that are above the kernel's space:
xfsdatad/0 S D7EE0342 6076 13 1 14 12 (L-TLB)
Many others just have zero or one for their PC:
scsi_eh_0 S 00000000 6084 14 1 15 13 (L-TLB)
kupdated S 00000001 5632 7 1 8 6 (L-TLB)
reply other threads:[~2003-05-12 0:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200305112032_MC3-1-386D-F200@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®