diff options
| author | Simon Glass <sjg@chromium.org> | 2021-03-22 18:21:01 +1300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2021-07-06 10:38:03 -0600 |
| commit | 85f718f64d65390f385111e57cfa017abd12879d (patch) | |
| tree | 060f095a5023d318577ebf074b7c6c288a3ef58e /arch/sandbox/include/asm/state.h | |
| parent | 1311dd37ecf476be041d0452d4ee38619aadd5de (diff) | |
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>
Diffstat (limited to 'arch/sandbox/include/asm/state.h')
| -rw-r--r-- | arch/sandbox/include/asm/state.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/sandbox/include/asm/state.h b/arch/sandbox/include/asm/state.h index bca13069824..1c4c571e28d 100644 --- a/arch/sandbox/include/asm/state.h +++ b/arch/sandbox/include/asm/state.h @@ -93,6 +93,7 @@ struct sandbox_state { bool ram_buf_read; /* true if we read the RAM buffer */ bool run_unittests; /* Run unit tests */ const char *select_unittests; /* Unit test to run */ + bool handle_signals; /* Handle signals within sandbox */ /* Pointer to information for each SPI bus/cs */ struct sandbox_spi_info spi[CONFIG_SANDBOX_SPI_MAX_BUS] |