RTEMS | Add another machine exception signal map test (!868)

[Joel Sherrill (@joel)]

Joel Sherrill commented on a discussion on testsuites/psxtests/psxsignal10/init.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/868#note_137029

 > +  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();

OK. Do we have any way to track which architectures/BSPs support this? I suspect this is another item in the list like libdl, libdebugger, Thread Local Storage, SMP, etc. that are not universally available and we do not have a good way to track. 

I am resolving this thread but it is a topic the project needs to figure out.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/868#note_137029
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/2fea6413/attachment-0001.htm>