I've been trying to learn how to use the "crash" dump analysis command on a live Fedora system and a live Ubuntu system. (To help me troubleshoot a networking problem.)
On Fedora, the "crash" command requires installation of kernel-debuginfo for the particular kernel you are running. On Ubuntu, I believe "crash" requires installation of linux-image-debug for the particular kernel you are running. I just noticed that Jim Doherty gave a lightning talk on systemTap last April. systemTap on Ubuntu also requires installation of linux-image-debug for the particular kernel you are running. On my multiboot PC, my Fedora and Ubuntu partitions are each 10 GB. I installed kernel-debuginfo on Fedora (and enabled the debuginfo repo). This was OK until there was a kernel update. The update caused my Fedora partition to run out of space. Q1: What is the easiest way to maintain a current kernel-debuginfo on my Fedora partition without repartitioning to a larger partition size? Q2: If I do repartition, how much space should I add to my Fedora partiton given that Yum keeps around several downlevel kernels? Q3: Same as Q2, for Ubuntu partition. Also, I've read that a current linux-image-debug is not available in a form that is usable by Apt. Q4: (General dump analysis question): Does anyone know of a "map" showing the layout of Linux kernel data structures in virtual memory? This would help in analyzing a kernel crash dump. I've searched and searched with no success. I've debugged a legacy commercial OS (MVS). There was a central vector table (CVT) at a standard location which was anchor for all of the MVS "control blocks". _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Sep 3 - Porkchop - The Areas of My Expertise Oct 1 - Ubikeys Oct 4 - Linux Fest Nov 5 - Releasing Open Source Software Dec 3 - TBD
