RTEMS | Add another machine exception signal map test (!868)
Joel Sherrill (@joel)
gitlab at rtems.org
Tue Dec 9 14:54:53 UTC 2025
Joel Sherrill started a new discussion on testsuites/psxtests/psxsignal10/init.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/868#note_137026
> + rtems_test_assert( !status );
> + status = sigdelset( &all_masked, SIGILL );
> + rtems_test_assert( !status );
> +
> + memset( &fault_act, 0, sizeof( fault_act ) );
> + fault_act.sa_handler = fault_handler;
> + fault_act.sa_mask = all_masked;
> +
> + status = sigprocmask( SIG_SETMASK, &fault_act.sa_mask, &oset );
> + rtems_test_assert( !status );
> + status = sigaction( SIGILL, &fault_act, &fault_oact );
> + rtems_test_assert( !status );
> +
> + if ( sigsetjmp( fault_jmp, 1 ) == 0 ) {
> + /* Generate machine exception */
> + _CPU_Instruction_illegal();
Will this test fail on many BSPs? This requires having an exception handler do the right thing. I don't think that's universally the case. @kinsey?
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/868#note_137026
You're receiving this email because of your account on gitlab.rtems.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251209/cb4969f1/attachment.htm>
More information about the bugs
mailing list