[[!meta copyright="Copyright © 2007, 2008, 2010, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] # Strategies * [[GDB]] -- the GNU debugger * [[gdb/Backtrace]]s * [[subhurd]] -- running another Hurd system in parallel * In context of [[glibc/debugging/ld_so_console]]: [[!message-id "20111108190129.750BC2C098@topped-with-meat.com"]] * [[rpctrace]] -- tracing [[RPC]]s * [[microkernel/mach/gnumach/interface/syscall/mach_print]] sycall # About Specific Packages * [[glibc]] * [[translator]]s * [[trap_in_the_kernel]] # IRC, freenode, #hurd, 2013-06-30 braunr: I don't understand your question totally, but I want to know how do you do this inspecting? i have a small test program that creates a thread, and inspect its state before any thread dies i use portinfo and rpctrace (there is also vminfo but you're not likely to need it for what you're doing right now) I have used rpctrace before, but portinfo, I will try it. is portinfo show a process's all port use log? not log current state dump the port name space? yes I found some names are not continuous. how this come out? continuous ? 101:send 103:send missing 102 some are freed a lot actually every RPC needs a reply port a temporary receive right to get replies from servers so we can reuse the name which are freed before of course