Re: [PATCH v2] target/ppc: check tb_env != 0 before printing TBU/TBL/DECR

On 7/14/22 13:17, Matheus K. Ferst wrote: On 14/07/2022 10:35, Daniel Henrique Barboza wrote: On 7/13/22 15:38, 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,

Re: [PATCH v2] target/ppc: check tb_env != 0 before printing TBU/TBL/DECR

On 14/07/2022 10:35, Daniel Henrique Barboza wrote: On 7/13/22 15:38, 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 th

Re: [PATCH v2] target/ppc: check tb_env != 0 before printing TBU/TBL/DECR

On 7/13/22 15:38, 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: https:

[PATCH v2] target/ppc: check tb_env != 0 before printing TBU/TBL/DECR

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 S