solaris调试技术.ppt

* * MT Debugging Although only 10% of Solaris applications are threaded, they are very critical to the platforms success. The Debugger (dbx) operates synchronously; when any thread or lightweight process (LWP) stops, all other threads and LWPs sympathetically stop. This behavior is referred to as the stop the world model. Supports both Solaris threads and POSIX threads Display status of all threads Examine stack traces of each thread Resume all threads step or next a specific thread Navigate between threads Lock information on individual threads (sync) Gdb vs. dbx for threads debugging; gdb doesnt do threads * MT Debugging - Thread Status * * * The Performance Analyzer is improved for this release. Actually two components: sampling collector and graphic analyzer Determines how and where time is spent in an application, down to the thread level. Reordering of applications with poor paging behavior Both CLI and GUI supported Replacement for ThreadAnalyzer (tha) Replacement for LoopTool New manual on using the Performance Analyzer/ Other Functions The Analyzer also provides the ability to add additional experiments to the current set, or drop experiments from the set. If the current set contains more than one experiment, sample selection is disabled: all samples from all experiments are shown. * The first part of the Performance Analyzer is the Sampling Collector. The term collector is used to describe the data collection features in dbx or the WorkShop debugger and the runtime support for those features in libcollector.so. The Sampling Collector can record a variety of different performance data, and convert each of them into metrics of performance computed against functions, callers and callees of any function, and against source and disassembly representations of the target program. It also records global data with periodic or manual sampling. Programs that will be targets for the collector may be compiled with any level of optimization, but must use dyna