On 2011-10-25 03:37, Wen Congyang wrote: > At 10/24/2011 11:58 PM, Dave Anderson Write: >> >> >> ----- Original Message ----- >> >>>>> No, an ELF image of the guest's physical memory. >>>> >>>> Well then that should be pretty straight forward to support. Depending >>>> upon >>>> how similar it would be to the "standard" kdump ELF format, the only other >>>> issue is how to determine the physical base address at which the kernel is >>>> loaded, in order to be able to translate the mapped kernel-text/static-data >>>> virtual region of the x86_64 arch (the __START_KERNEL_map region). >>>> >>> >>> I guess an elf note would work for that? >> >> Right -- here is an example of a RHEL6 ELF kdump header: > > Hi, Jan > Is gdb standard core file like the following format? Does gdb support this > format? > > If yes, I think the dump command can output the guest physical memory in > the following format, and we can use both gdb and crash to analyze it.
That would be ideal. But given lacking crash-like add-ons for vanilla gdb, it makes sense to focus on crash compatibility for now. I suspect we will need some changes to gdb anyway to make use of all information the kdump file contains. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux
