On Wed, Jul 23, 2014 at 6:37 PM, Dave Anderson <anderson@xxxxxxxxxx> wrote: > > > ----- Original Message ----- >> >> Here is my counter-proposal, where the invocation would be something >> like this: >> >> $ crash vmlinux ramdump@address [-o output_file] >> >> and if there are multiple images, make them a comma-separated list: >> >> $ crash vmlinux ramdump1@address,ramdump2@address [-o output_file] >> > > FYI, if you view the above in the web archives, it seems that it > strips out ampersands, so it looks like "ramdump address" instead > of "ramdump@address". > > So just in case you're confused by that, it's a single argument > with an ampersand separating the filename and address. > Modified patch attached. It is rebased to latest crash version. The arguments are in the form of ordered pair as you had mentioned. I have tested it with arm and armv8 ramdumps. Do we really need dump_ramdump_def ? As the dump is converted to kdump and we use the kdump flag in pc->flags, help -D and help -n works fine using kdump dump functions. Did I miss something ? I will send you the link to arm64 ramdump in another email. Thanks, Vinayak
Attachment:
0001-raw-RAM-image-support.patch
Description: Binary data
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
