u-boot/arch/sandbox
Heinrich Schuchardt a2a9317cbc sandbox: unblock signal before calling execv()
The following faulty behavior was observed. The sandbox configured with
CONFIG_SANDBOX_CRASH_RESET=y was invoked with

    ./u-boot -T -S

After executing `exception undefined' the sandbox reboots.
When executing `exception undefined' the sandbox exits with SIGSEGV.

The expected behavior is that the sandbox should reboot again.

If we are relaunching the sandbox in a signal handler, we have to unblock
the respective signal before calling execv(). See signal(7) man-page.

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
2022-09-25 08:30:05 -06:00
..
cpu sandbox: unblock signal before calling execv() 2022-09-25 08:30:05 -06:00
dts dm: core: Add functions to read 8/16-bit integers 2022-09-14 15:23:03 -04:00
include/asm bootstd: Allow EFI bootmgr to support an invalid bootflow 2022-08-12 08:17:10 -04:00
lib sandbox: Rename EFI runtime sections 2022-06-23 12:58:18 -04:00
config.mk sandbox: Add libfuzzer integration 2022-06-23 12:58:18 -04:00
Kconfig sandbox: raise SANDBOX_RAM_SIZE_MB default to 256 2022-06-28 03:09:51 +01:00
Makefile sandbox: fix build failure with musl and SDL 2022-02-09 12:26:12 -07:00