Show simple item record

dc.contributor.authorVenkateswaran, Sreekrishnanen_US
dc.date.accessioned2017-12-12T03:03:41Z
dc.date.available2017-12-12T03:03:41Z
dc.date.issued2010en_US
dc.identifier.isbn9780136123545en_US
dc.identifier.isbn0136123546en_US
dc.identifier.otherHPU5160865en_US
dc.identifier.urihttps://lib.hpu.edu.vn/handle/123456789/28479
dc.description.abstractDebugging Linux Systems discusses the main tools available today to debug 2.6 Linux Kernels. We start by exploring the seemingly esoteric operations of the Kernel Debugger (KDB), Kernel GNU DeBugger (KGDB), the plain GNU DeBugger (GDB), and JTAG debuggers. We then investigate Kernel Probes, a feature that lets you intrude into a kernel function and extract debug information or apply a medicated patch. Analyzing a crash dump can yield clues for postmortem analysis of kernel crashes or hangs, so we take a look at Kdump, a serviceability tool that collects a system dump after spawning a new kernel. Profiling points you to code regions that burn more CPU cycles, so we learn to use the OProfile kernel profiler and the gprof application profiler to sense the presence of code bottlenecks. Because tracing provides insight into behavioral problems that manifest during interactions between different code modules, we delve into the Linux Trace Toolkit, a system designed for high-volume trace capture.en_US
dc.format.extent90 p.en_US
dc.format.mimetypeapplication/pdfen_US
dc.language.isoenen_US
dc.publisherPearson Education en_US
dc.subjectLinux Systemsen_US
dc.subjectDebugging Linux Systemsen_US
dc.subjectLinux Kernelsen_US
dc.titleDebugging Linux Systemsen_US
dc.typeBooken_US
dc.size890Kben_US
dc.departmentTechnologyen_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record