时间:2021-05-19
今天在Linux上调试程序程序的时候发现有时候程序会莫名其妙的hang住,于是就想能不能找到当时程序有那些线程,都在做什么。找了一下linux命令,还真可以满足我的需求。下面看一个小例子。
先准备一段程序,为了简单起见这里使用python来写,其中创建了两个线程来执行各自的任务。
import threadingimport timedef test1(): while(True): time.sleep(1) print 'test1'def test2(): while(True): time.sleep(1) print 'test2't1 = threading.Thread(target=test1, args=())t2 = threading.Thread(target=test2, args=())t1.start()t2.start()time.sleep(12345)然后运行这个程序
$ python test.py先使用 “pstree -apl ” 查看进程结构
$ pstree -apl 26855python,26855 test.py |-{python},26858 |-{python},26859然后使用 “ps -Lf ” 查看线程信息
$ ps -Lf 26855UID PID PPID LWP C NLWP STIME TTY STAT TIME CMDjhadmin 26855 25902 26855 0 3 15:15 pts/5 Sl+ 0:00 python test.pyjhadmin 26855 25902 26858 0 3 15:15 pts/5 Sl+ 0:00 python test.pyjhadmin 26855 25902 26859 0 3 15:15 pts/5 Sl+ 0:00 python test.py最后,可以使用 “pstack ” 查看线程的详细信息,如下:
$ pstack 26855Thread 3 (Thread 0x7f8a344f2700 (LWP 26858)):#0 0x00007f8a3b5387a3 in select () from /lib64/libc.so.6#1 0x00007f8a344f5070 in time_sleep () from /usr/lib64/python2.7/lib-dynload/timemodule.so#2 0x00007f8a3c215af0 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#3 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#4 0x00007f8a3c1a188d in function_call () from /lib64/libpython2.7.so.1.0#5 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#6 0x00007f8a3c2104fd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#7 0x00007f8a3c2154bd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#8 0x00007f8a3c2154bd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#9 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#10 0x00007f8a3c1a1798 in function_call () from /lib64/libpython2.7.so.1.0#11 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#12 0x00007f8a3c18b8d5 in instancemethod_call () from /lib64/libpython2.7.so.1.0#13 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#14 0x00007f8a3c20e6f7 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0#15 0x00007f8a3c2465c2 in t_bootstrap () from /lib64/libpython2.7.so.1.0#16 0x00007f8a3bf1ce25 in start_thread () from /lib64/libpthread.so.0#17 0x00007f8a3b54134d in clone () from /lib64/libc.so.6Thread 2 (Thread 0x7f8a33cf1700 (LWP 26859)):#0 0x00007f8a3b5387a3 in select () from /lib64/libc.so.6#1 0x00007f8a344f5070 in time_sleep () from /usr/lib64/python2.7/lib-dynload/timemodule.so#2 0x00007f8a3c215af0 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#3 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#4 0x00007f8a3c1a188d in function_call () from /lib64/libpython2.7.so.1.0 #5 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0 #6 0x00007f8a3c2104fd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0 #7 0x00007f8a3c2154bd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0 #8 0x00007f8a3c2154bd in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0 #9 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#10 0x00007f8a3c1a1798 in function_call () from /lib64/libpython2.7.so.1.0#11 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#12 0x00007f8a3c18b8d5 in instancemethod_call () from /lib64/libpython2.7.so.1.0#13 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#14 0x00007f8a3c20e6f7 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0#15 0x00007f8a3c2465c2 in t_bootstrap () from /lib64/libpython2.7.so.1.0#16 0x00007f8a3bf1ce25 in start_thread () from /lib64/libpthread.so.0#17 0x00007f8a3b54134d in clone () from /lib64/libc.so.6Thread 1 (Thread 0x7f8a3c6f3740 (LWP 26855)):#0 0x00007f8a3bf22a0b in do_futex_wait.constprop.1 () from /lib64/libpthread.so.0#1 0x00007f8a3bf22a9f in __new_sem_wait_slow.constprop.0 () from /lib64/libpthread.so.0#2 0x00007f8a3bf22b3b in sem_wait@@GLIBC_2.2.5 () from /lib64/libpthread.so.0#3 0x00007f8a3c242535 in PyThread_acquire_lock () from /lib64/libpython2.7.so.1.0#4 0x00007f8a3c2461c2 in lock_PyThread_acquire_lock () from /lib64/libpython2.7.so.1.0#5 0x00007f8a3c215af0 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#6 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#7 0x00007f8a3c21533c in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#8 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#9 0x00007f8a3c21533c in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0#10 0x00007f8a3c217e3d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0#11 0x00007f8a3c1a1798 in function_call () from /lib64/libpython2.7.so.1.0#12 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#13 0x00007f8a3c18b8d5 in instancemethod_call () from /lib64/libpython2.7.so.1.0#14 0x00007f8a3c17c8e3 in PyObject_Call () from /lib64/libpython2.7.so.1.0#15 0x00007f8a3c17c9c5 in call_function_tail () from /lib64/libpython2.7.so.1.0#16 0x00007f8a3c17ccfb in PyObject_CallMethod () from /lib64/libpython2.7.so.1.0#17 0x00007f8a3c232f29 in Py_Finalize () from /lib64/libpython2.7.so.1.0#18 0x00007f8a3c244325 in Py_Main () from /lib64/libpython2.7.so.1.0#19 0x00007f8a3b46ac05 in __libc_start_main () from /lib64/libc.so.6#20 0x000000000040071e in _start ()这里多说一句,如果要看java程序的栈信息,可以使用 “kill -3 ” 来查看,比如:
$ nohub java Test > test.out &$ kill -3 <pid>以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持。
声明:本页内容来源网络,仅供用户参考;我单位不保证亦不表示资料全面及准确无误,也不保证亦不表示这些资料为最新信息,如因任何原因,本网内容或者用户因倚赖本网内容造成任何损失或损害,我单位将不会负任何法律责任。如涉及版权问题,请提交至online#300.cn邮箱联系删除。
前言在Linux系统下面,top命令可以查看查看stopped进程。但是不能查看stopped进程的详细信息。那么如何查看stopped进程,并且杀掉这些sto
linux下我们可以调用fork函数创建子进程,创建的子进程将会得到父进程的数据空间、堆、栈......副本(采用写时复制机制),子进程将会继承父进程的信号掩码
Linux系统的进程是由线程组成的,当然Linux进程下的线程数是不固定的,可以是一个进程,也可以是多个进程。下面就由小编和大家讲一讲linux查看进程。进程是
详解进程、线程和协程的区别首先,给出“进程、线程和协程”的特点:进程:拥有自己独立的堆和栈,既不共享堆,也不共享栈,进程由操作系统调度;线程:拥有自己独立的栈和
有时候一些程序员,或者网络人士在进行电脑维护和调试时需要查看电脑目前的进程详细信息,那么该如何查看呢?下面小编就为大家介绍电脑DOS命令查看进程详细信息方法,不