[PATCH] sandbox: Adjust configuration to hang on panic()

Heinrich Schuchardt xypron.glpk at gmx.de
Wed Jan 1 12:32:10 CET 2025


On 12/20/24 04:59, Simon Glass wrote:
> It is annoying to have sandbox enter a boot loop when an assertion
> fails. Hang instead, since then the error message is only printed once
> and Ctrl-C can be used to quit, as per normal.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
>
>   configs/sandbox_defconfig | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/configs/sandbox_defconfig b/configs/sandbox_defconfig
> index 3de4aa79c6d..636130a360d 100644
> --- a/configs/sandbox_defconfig
> +++ b/configs/sandbox_defconfig
> @@ -354,6 +354,7 @@ CONFIG_WDT_FTWDT010=y
>   CONFIG_FS_CBFS=y
>   CONFIG_FS_CRAMFS=y
>   CONFIG_ADDR_MAP=y
> +CONFIG_PANIC_HANG=y

Command line option -S is used for running the UEFI SCT. We need the
sandbox to reboot and to allow the SCT to report the failed test.

This patch is not needed. You can already exit the assertion caused loop
with CTRL-C.

Best regards

Heinrich

>   CONFIG_CMD_DHRYSTONE=y
>   CONFIG_MBEDTLS_LIB=y
>   CONFIG_ECDSA=y



More information about the U-Boot mailing list