Kinsey Moore commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5364#note_135514


The `rtems_debugger_target_start_memory_access()` macro contains a setjmp and 
since it gets set to a variable this counts as undefined behavior as we've 
previously had conversations about. The `ui` variable in `hex_decode_address()` 
is an odd one, but may be getting caught because the function is inlined. All 
the uses of `setjmp()` in `rtems-debugger-server.c` need to be audited.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5364#note_135514
You're receiving this email because of your account on gitlab.rtems.org.


_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs

Reply via email to