It just means that the process 25062 exited after pidof listed it but before eu-stack had queried its state, and process 25068 was tearing down at the same time the stack trace was being built and as a result the stack building failed while reading the executable pointed via proc filesystem. If you get an errors such as eu-stack: dwfl_linux_proc_report pid 25062: No such file or directoryĮu-stack: dwfl_linux_proc_report pid 25068: Exec format error Pidof apache2 | sort -n | sudo xargs -rn1 timeout 1s eu-stack -id -p > snap2Īnd you can identify stacks that did not change during 10 seconds (the sort is needed to make the stack order stable so you can meaningfully compare the outputs). Pidof apache2 | sort -n | sudo xargs -rn1 timeout 1s eu-stack -id -p > snap1 Set timeout longer if you're willing to wait longer to get the stack.Īnd if you have a busy system where only some of the threads or processes are locked, one can take a snapshot of current process states like this sudo true The timeout is used to prevent stalling on processes in uninterruptible sleep (some more recent kernel versions may allow getting stacks for those processes, too). Pidof chrome | sudo xargs -rn1 timeout 1s eu-stack -id -p For example, to list all thread stacks for the Google Chrome (which is running multiple processes and threads!) one can do sudo true The hex numbers you are seeing are memory addresses, so these need to be converted at runtime to the appropriate object metadata and sent. One can write one-liners for more complex stuff. The crash stack trace does include the method name by default (mangled), but additional information like the file name and line number needs to be uploaded at app runtime.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |