Typo

Like kdump and merino lets call this one more format raw_ramdump_elf32

Like kdump and netdump lets call this one more format raw_ramdump_elf32

Sent from Yahoo Mail on Android


From: paawan oza <paawan1982@yahoo.com>;
To: Dave Anderson <anderson@redhat.com>; Discussion list for crash utility usage, maintenance and development <crash-utility@redhat.com>;
Subject: Re: [Crash-utility] how to use crash utility to parse the binary memory dump
Sent: Wed, May 28, 2014 3:54:52 PM

Hi Dave,

I am typing this reply from phone, so keeping it short, will give elaborate reply tomorrow if need.

I am doing it in one step only,
If you give something like below

Crash vmlinux bin_file kernel_base

Crashutility creates virtual elf32
once you exit crash, crash will delete temporary arm elf file which we created in one step process.

It will look like vmcore, but actually it is just conversion to elf, in fact vmcore is in elf format,

Like kdump and merino lets call this one more format raw_ramdump_elf32

Regards,
Oza

Sent from Yahoo Mail on Android


From: Dave Anderson <anderson@redhat.com>;
To: paawan oza <paawan1982@yahoo.com>; Discussion list for crash utility usage, maintenance and development <crash-utility@redhat.com>;
Subject: Re: [Crash-utility] how to use crash utility to parse the binary memory dump
Sent: Wed, May 28, 2014 1:28:24 PM



----- Original Message -----
> Hi,
>
> I have modified crash utility to convert ramdump to ELF32 format.
>
> @Dave: this is very helpful feature where if someone wants to debug raw ramdump.
> no matter where you kenerel starts, I make one program header with relevant
> offset and generate object files.
> the code for the same is embedded in the crash utlity.
>
> Dave, please share your views on this.
>
> Regards,
> Oza.

Since these raw DDR dumps seem to be an existing feature, it certainly
seems worth implementing support for them. 

I'm curious as to how these RAM dumps are currently used -- are there other
tools that use them somehow? 

Are these DDR RAM dumps specific to embedded 32-bit ARM machines?
 
Your feature sounds like a two-stage process:

(1) invoke crash utility -- passing it the base physical address of the
    contiguous RAM dump, and the RAM dump file name(s) -- and then crash
    creates a single ELF vmcore by pre-pending an ELF header and concatenating
    the dump file names.
(2) invoke crash utility with vmlinux and newly-created vmcore.

But you mention "generate object files" above.  Do you generate more than one file?

Is the newly-created vmcore subsequently recognized as a netdump or kdump
ELF vmcore?  (i.e, handled by existing code in netdump.c) 

Or does it create a new ELF-like dumpfile type that is handled in your new
ramdump.c file?

Could it be done in one step?  In other words, something like:

  $ crash vmlinux --ddr 80000000 ddr1.bin [ddr2.bin ...]

where there would be a "virtual" ELF header created that could be used
during the crash session?  (perhaps with an optional "-o outputfile"
command line option to create/save it as an ELF vmcore)

Dave

 
>
>
>
>
> On Tuesday, 27 May 2014 5:34 PM, buyitian <buyit@live.cn> wrote:
>
>
> 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
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility