u-boot/arch/sandbox/cpu
Simon Glass 85f718f64d sandbox: Support signal handling only when requested
At present if sandbox crashes it prints a message and tries to exit. But
with the recently introduced signal handler, it often seems to get stuck
in a loop until the stack overflows:

Segmentation violation

Segmentation violation

Segmentation violation

Segmentation violation

Segmentation violation

Segmentation violation

Segmentation violation
...

The signal handler is only useful for a few tests, as I understand it.
Make it optional.

Signed-off-by: Simon Glass <sjg@chromium.org>
2021-07-06 10:38:03 -06:00
..
cache.c sandbox: implement invalidate_icache_all() 2020-12-22 20:39:25 -07:00
cpu.c sandbox: Correct uninit conflict 2021-03-27 15:04:31 +13:00
eth-raw-os.c sandbox: eth-raw: do not close the console input 2020-11-05 09:11:30 -07:00
Makefile sandbox: implement invalidate_icache_all() 2020-12-22 20:39:25 -07:00
os.c sandbox: use sections instead of symbols for getopt array boundaries 2021-05-24 14:21:30 -04:00
sdl.c reset: Remove addr parameter from reset_cpu() 2021-03-02 14:03:02 -05:00
spl.c sandbox: Update os_find_u_boot() to find the .img file 2021-03-12 09:57:31 -05:00
start.c sandbox: Support signal handling only when requested 2021-07-06 10:38:03 -06:00
state.c sandbox: Write out bloblist when exiting 2021-03-02 15:53:37 -05:00
u-boot-spl.lds sandbox: use sections instead of symbols for getopt array boundaries 2021-05-24 14:21:30 -04:00
u-boot.lds sandbox: use sections instead of symbols for getopt array boundaries 2021-05-24 14:21:30 -04:00