On 3/4/24 10:59, Gustavo Romero wrote:
Perhaps just abort for SIGABRT instead?
Although this can make a simpler test, the test can't control
the si_addr value easily, which I think is interesting to be tested.
Why do you prefer SIGABRT?
I missed that you were testing si_addr -- in which case SIGSEGV is a good match.
A test using setitimer to raise SIGALRM would test the async path.
SIGLARM doesn't generate any interesting siginfo?
It should at minimum have si_sig = SIGALRM.
gromero@arm64:~$ gdb -q ./sigalrm
Reading symbols from ./sigalrm...
(gdb) run
Starting program: /home/gromero/sigalrm
Program terminated with signal SIGALRM, Alarm clock.
The program no longer exists.
(gdb) p $_siginfo
$1 = void
Well that's because the program died.
Do you need to have gdb handle the signal?
r~
