On Sun, 30 Jul 2023 at 20:52, Viktor Prutyanov
wrote:
>
>
> >> On 2023/06/12 12:42, Viktor Prutyanov wrote:
> >>
> Prcb may be set to 0 for some CPUs if the dump was taken before they
> start. The dump may still contain valuable information for started CPUs
> so don't abandon conver
>> On 2023/06/12 12:42, Viktor Prutyanov wrote:
>>
Prcb may be set to 0 for some CPUs if the dump was taken before they
start. The dump may still contain valuable information for started CPUs
so don't abandon conversion in such a case.
Signed-off-by: Akihiko Odaki
-
> On 2023/06/12 12:42, Viktor Prutyanov wrote:
>
>>> Prcb may be set to 0 for some CPUs if the dump was taken before they
>>> start. The dump may still contain valuable information for started CPUs
>>> so don't abandon conversion in such a case.
>>>
>>> Signed-off-by: Akihiko Odaki
>>> ---
>>>
On 2023/06/12 12:42, Viktor Prutyanov wrote:
Prcb may be set to 0 for some CPUs if the dump was taken before they
start. The dump may still contain valuable information for started CPUs
so don't abandon conversion in such a case.
Signed-off-by: Akihiko Odaki
---
contrib/elf2dmp/main.c | 5 +
> Prcb may be set to 0 for some CPUs if the dump was taken before they
> start. The dump may still contain valuable information for started CPUs
> so don't abandon conversion in such a case.
>
> Signed-off-by: Akihiko Odaki
> ---
> contrib/elf2dmp/main.c | 5 +
> 1 file changed, 5 insertions(+
Prcb may be set to 0 for some CPUs if the dump was taken before they
start. The dump may still contain valuable information for started CPUs
so don't abandon conversion in such a case.
Signed-off-by: Akihiko Odaki
---
contrib/elf2dmp/main.c | 5 +
1 file changed, 5 insertions(+)
diff --git
