On Fri, Dec 08, 2006 at 05:50:51PM +0900, Ken'ichi Ohmichi wrote: > > Hi. > > makedumpfile version 1.0.7 is released. > Please test it. Your opinions/comments are welcome. > I've been looking it over, and will be pulling it in to the next kexec-tools build
My only comment relates to the ELF32/64 bit headers. I was under the impression that the gelf library had some functionality in it to abstract the 64/32 bit difference out so that separate code paths or casts weren't needed for each, but I'm having trouble figuring out if that is actually the case. I may come back to that issue, but for now, your solution looks a-ok to me. thanks and regards Neil > Note: > The latest crash utility (4.0-3.14) can read the ELF dumpfile > created by makedumpfile (with -E option). Thank you, Dave. > https://www.redhat.com/archives/crash-utility/2006-December/msg00002.html > > Explanation of makedumpfile: > To shorten the size of the dumpfile and the time of creating the > dumpfile, makedumpfile copies only the necessary pages for analysis > to the dumpfile from /proc/vmcore. You can specify the kind of > unnecessary pages with dump_level. If you want to shorten the size > further, enable the compression of the page data. > > Pathset: > [1/5] Add the handling of both ELF32 and ELF64 vmcore > A new makedumpfile can handle both ELF32 and ELF64 vmcore. > The existing makedumpfile handles /proc/vmcore as ELF64 though user > can specify ELF32 or ELF64 on i386. If user specifies ELF32 vmcore > when 2nd-kernel is loaded, makedumpfile cannot create the dumpfile > correctly. > > [2/5] Cleanup the DWARF code > This patch clean up the DWARF code for the next patch. > > [3/5] Add get_array_length() > This patch adds get_array_length() for getting the MAX_ORDER value > dynamically. The MAX_ORDER value is the number of the array > "zone.free_area[]" that depends on CONFIG_FORCE_MAX_ZONEORDER, > and it is included in the debug information of the kernel file. > makedumpfile gets it by analyzing the debug information. > > [4/5] Fix help comment > This patch deletes the following comment because the latest crash > utility (4.0-3.14) can analyze the ELF dumpfile created by makedumpfile. > > "THIS IS ONLY FOR GDB. NOT FULLY READABLE FROM THE CRASH UTILITY." > > [5/5] Update the version information > makedumpfile 1.0.7 > > > If there is an old config file created by makedumpfile (-g option), > please delete it and recreate it by a new makedumpfile. > > > The latest makedumpfile(ver. 1.0.7) is based on makedumpfile from > me(2006/11/24) with all my patches applied. > You can get the latest makedumpfile from the following URL. > https://sourceforge.net/projects/makedumpfile/ > > Method of installation: > You can compile the makedumpfile command as follows; > 1. "tar -zxvf makedumpfile-1.0.7.tar.gz" > 2. "cd makedumpfile" > 3. "make; make install" > > Usage: > makedumpfile [-c] [-E] [-d dump_level] [-x vmlinux] dump_mem dump_file > > Example: > If you want to exclude pages filled by zero, cache pages, user pages > and free pages and to enable compression, please execute the following > command. > > # makedumpfile -c -d 31 -x vmlinux /proc/vmcore dumpfile > > Todo: > - Dumping DISCONTIGMEM kernel > > Thanks > Ken'ichi Ohmichi -- /*************************************************** *Neil Horman *Software Engineer *Red Hat, Inc. [EMAIL PROTECTED] *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/ _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
