On 3/4/24 2:18 PM, Richard Henderson wrote:
On 3/3/24 09:26, Gustavo Romero wrote:
+ /* Filter out si_type from si_code. See comment in siginfo_noswap(). */ > +
tmp_siginfo = ts->sync_signal.info;
+ tmp_siginfo.si_code = sextract32(tmp_siginfo.si_code, 0, 16);
This is incorrect, as
On 3/3/24 09:26, Gustavo Romero wrote:
+/* Filter out si_type from si_code. See comment in siginfo_noswap(). */ > +
tmp_siginfo = ts->sync_signal.info;
+tmp_siginfo.si_code = sextract32(tmp_siginfo.si_code, 0, 16);
This is incorrect, as it only handles synchronous signals.
In hand
Add stub to handle Xfer:siginfo:read query that requests the machine's
siginfo data.
This is used when GDB users execute 'print $_siginfo' and when the
machine stops due to a signal, like on a SIGSEGV. The information in
siginfo allows GDB to determine further details on the signal, like the
fault