From: Richard Henderson <richard.henderson@linaro.org>
To: Gustavo Romero <gustavo.romero@linaro.org>,
qemu-devel@nongnu.org, alex.bennee@linaro.org
Cc: peter.maydell@linaro.org
Subject: Re: [PATCH 2/2] tests/tcg: Add multiarch test for Xfer:siginfo:read stub
Date: Mon, 4 Mar 2024 12:51:55 -1000 [thread overview]
Message-ID: <cd6b5e0f-5a10-4acb-94d6-51073ceb5acf@linaro.org> (raw)
In-Reply-To: <d98ef081-b25d-4dbf-7b67-fe27e09ff2f0@linaro.org>
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~
next prev parent reply other threads:[~2024-03-04 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 19:26 [PATCH 1/2] gdbstub: Add Xfer:siginfo:read stub Gustavo Romero
2024-03-03 19:26 ` [PATCH 2/2] tests/tcg: Add multiarch test for " Gustavo Romero
2024-03-04 17:21 ` Richard Henderson
2024-03-04 20:59 ` Gustavo Romero
2024-03-04 22:51 ` Richard Henderson [this message]
2024-03-07 17:50 ` Gustavo Romero
2024-03-07 19:31 ` Richard Henderson
2024-03-08 14:59 ` Gustavo Romero
2024-03-04 17:18 ` [PATCH 1/2] gdbstub: Add " Richard Henderson
2024-03-07 17:51 ` Gustavo Romero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd6b5e0f-5a10-4acb-94d6-51073ceb5acf@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).