Hi Dave,
this is excatly I wrote in previous mail....have ELF header and one program header.
I do have modified version of crash utlity (it is quiet a bit of code) (introduced ramdump.c)
I feel it is better to ahve that feature integrated into crash utility for raw ramdump.
Regards,
Oza.
On Tuesday, 27 May 2014 7:05 PM, Dave Anderson <anderson@xxxxxxxxxx> wrote:
----- Original Message -----
> Hi：
>
> my HW is like this:
>
> DDR starts from physical address 0x80000000, size is 1GB.
> after crash, there are two dump files: ddr1.bin and ddr2.bin.
> each binary file is 512MB.
>
> the vmlinux is on my hand.
>
> how can i use crash utility to parse these two binary?
> thanks.
>
> Best Regards
I'm presuming that these binary files are generated from a 32-bit ARM
machine?
Anyway, if it's just a raw dump of physical memory, the crash utility
cannot do anything with them. Crash supports over 20 different dumpfile
formats, but they all have dumpfile headers that describe what's
contained in the file.
It seems to me that there might have been a discussion on this list
a while ago about the pre-pending of an ELF header to a raw, memory-only,
ARM dump? Perhaps the ARM users on this list have some recollection?
Dave
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
