Hi Kevin, I uploaded makedumpfile-1.3.0-rc01.tar.gz to the following URL for avoiding a tab/space issue: https://sourceforge.net/project/downloading.php?group_id=178938&use_mirror=nchc&filename=makedumpfile-1.3.0-rc01.tar.gz&75638452 Could you use this ? Ken'ichi Ohmichi wrote: >> worthk:~/makedumpfile-1.2.9$ patch -l -p1 --dry-run <v1.3.0-rc01.patch >> patching file Makefile >> Hunk #1 succeeded at 1 with fuzz 1. >> patching file ia64.c >> patching file makedumpfile-R.pl >> patching file makedumpfile.c >> patching file makedumpfile.h >> patching file x86.c >> patching file x86_64.c >> >> The fuzz messages is because I'm patching against a makefile that was >> modified by Ubuntu to use "-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE" >> rather than "-D_FILE_OFFSET_BITS=64". Perhaps the difference between >> the Ubuntu version and this upstream setting should be resolved... >> Ubuntu changelog at https://launchpad.net/ubuntu/+source/makedumpfile >> with note "Use _LARGEFILE_SOURCE and _LARGEFILE64_SOURCE instead of >> _FILE_OFFSET_BITS=64 for correct compilation." Could this have negative >> effects or is it just a different way to tell the compiler to support >> large files? >> >> CFLAGS = -g -O2 -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE \ >> -DVERSION='"$(VERSION)"' -DRELEASE_DATE='"$(DATE)"' >> CFLAGS_ARCH = -g -O2 -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > > I will consider it. I see that the problem occurs by the above change. On my ubuntu kernel (built by your kernel config file), makedumpfile-1.3.0-rc01 can work fine like the following: # makedumpfile -cd31 -x vmlinux /proc/vmcore dump Copying data : [100 %] The dumpfile is saved to dump. makedumpfile Completed. # But makedumpfile-1.3.0-rc01 with the above change of Makefile cannot work with the following message: # makedumpfile -cd31 -x vmlinux /proc/vmcore dump open_dump_memory: Can't open the dump memory(vmcore). File too large makedumpfile Failed. # Could you test makedumpfile-1.3.0-rc01 without any change ? Thanks Ken'ichi Ohmichi
