Red Hat Enterprise Linux 5 Administration Unleashed

442CHAPTER 21Monitoring and Tuning the KernelLISTING 21.5ContinuedType “show copying” to see the conditions.There is absolutely no warranty for GDB. Type “show warranty” for details.This GDB was configured as “x86_64-unknown-linux-gnu”...KERNEL: /usr/lib/debug/lib/modules/2.6.18-1.2747.el5/vmlinuxDUMPFILE: vmcoreCPUS: 2DATE: Fri Jan 12 15:31:26 2007UPTIME: 00:04:20LOAD AVERAGE: 0.31, 0.31, 0.14TASKS: 168NODENAME: myhostnameRELEASE: 2.6.18-1.2747.el5VERSION: #1 SMP Thu Nov 9 18:52:11 EST 2006MACHINE: x86_64 (2400 Mhz)MEMORY: 2 GBPANIC: “SysRq : Trigger a crashdump”PID: 4254COMMAND: “bash”TASK: ffff81007fb02040 [THREAD_INFO: ffff810060036000]CPU: 0STATE: TASK_RUNNING (SYSRQ)crash>After you receive the crash> prompt, you can execute any of the crash commands listedin the man page (execute man crash to view) to analyze the vmcore file. For example, thevm command shows basic virtual memory information, and the bt command shows thebacktrace. The information shown for each of these commands is what was stored inmemory at the time of the system crash.TIPAt the crash> prompt, type help at any time to display a list of commands. You canalso type help to display help for a specific command.The default editor used when in a crash session is Vi. To change to the Emacs editor,create a .crashrc file in your home directory with the following line:set emacsThis setting must be configured per user. To specifically set Vi as the editor during thecrash session, include the following line in a .crashrc file in your home directory:set vi