Re: xmon memory dump does not handle LE

[Douglas Miller <dougmill@linux.vnet.ibm.com>]

Hi Michael,

Yes, your patch seems a more complete solution. The idea of "d1", "d2", 
"d4", and "d8" commands is more what I needed and makes more sense to 
someone hitting xmon "cold". I'll work on getting your patch submitted.


Question on these sorts of patches (PPC only), do we submit initially to 
upstream, or here on this (PPC) mailing list? It would be nice to get 
this into the distros as soon as possible.

Thanks,

Doug


On 02/03/2017 04:31 AM, Michael Ellerman wrote:
> Douglas Miller <dougmill@linux.vnet.ibm.com> writes:
>
>> I'm referring to the three commands listed in the help:
>>
>> d     dump bytes
>>
>> df    dump float values
>>
>> dd    dump double values
>>
>> As it turns out, all three of these commands do exactly the same thing,
>> and it's certainly not what I'd expect based on experience with other
>> debuggers. Maybe the original intent was only to simply output bytes of
>> memory, but to me the help implies otherwise and certainly something
>> more is needed.
> OK. I don't think df/dd actually exist in the code, so I think the help
> is just out of date, by about 20 years.
>
> 'd' definitely works as intended and does what the help says as far as
> I'm concerned. The output is pretty similar to hexdump -C for example.
>
> Also xmon isn't a debugger it's a crash handler :)
>
>> I'll take a look at Balbir's patch and see if I can help move it along.
> Actually take a look at mine instead.
>
> cheers
>