Re: [RFC PATCH] target/ppc: don't print TB in ppc_cpu_dump_state if it's not initialized

2022-07-13 Thread Matheus K. Ferst
On 12/07/2022 23:21, David Gibson wrote: On Tue, Jul 12, 2022 at 06:13:44PM -0300, Daniel Henrique Barboza wrote: On 7/12/22 16:25, Matheus Ferst wrote: When using "-machine none", env->tb_env is not allocated, causing the segmentation fault reported in issue #85 (launchpad bug #811683). To

Re: [RFC PATCH] target/ppc: don't print TB in ppc_cpu_dump_state if it's not initialized

2022-07-12 Thread David Gibson
On Tue, Jul 12, 2022 at 06:13:44PM -0300, Daniel Henrique Barboza wrote: > > > On 7/12/22 16:25, Matheus Ferst wrote: > > When using "-machine none", env->tb_env is not allocated, causing the > > segmentation fault reported in issue #85 (launchpad bug #811683). To > > avoid this problem, check

Re: [RFC PATCH] target/ppc: don't print TB in ppc_cpu_dump_state if it's not initialized

2022-07-12 Thread Daniel Henrique Barboza
On 7/12/22 16:25, Matheus Ferst wrote: When using "-machine none", env->tb_env is not allocated, causing the segmentation fault reported in issue #85 (launchpad bug #811683). To avoid this problem, check if the pointer != NULL before calling the methods to print TBU/TBL/DECR. Resolves:

[RFC PATCH] target/ppc: don't print TB in ppc_cpu_dump_state if it's not initialized

2022-07-12 Thread Matheus Ferst
When using "-machine none", env->tb_env is not allocated, causing the segmentation fault reported in issue #85 (launchpad bug #811683). To avoid this problem, check if the pointer != NULL before calling the methods to print TBU/TBL/DECR. Resolves: https://gitlab.com/qemu-project/qemu/-/issues/85