Re: how to use crash utility to parse the binary memory dump

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




----- Original Message -----
> Hi Dave,
> 
> Sometime back I proposed this thing, but I did not get enough time + some
> approvals to post a patch.
> now you have patches coming in for the same idea. :)
> I looked at the patch, and I fully agree with you that creating one
> more-ramdump file is not a good idea, it wastes the space and creates
> redundancy.
> 
> I think can pull out implementation I have done in my current organisation,
> and it is closer to what you are hinting.
> 64bit ELF header should do the trick for addressing both 32bit and 64bit,
> which also I think can be taken care.
> 
> Regards,
> Oza.

Hello Oza,

I do recall our discussions.  Since both you and Vinayak use non-work
email addresses, I thought maybe you both worked for the same company,
and he had taken over the task.  ;-)

I do like the simplicity of Vinayak's latest patch-set, but it would be
ideal if it could be restricted to 64-bit and just use the original RAM
dump file.  It's also reasonable to offer an option to save it as 
separate ELF file.  So I don't think it would take much to update his
patch to get that done. 

But certainly you can post your version, or perhaps patch Vinayak's,
as long as the end result covers the requests above.

Thanks,
  Dave
 

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility




[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux