The mach exception data received in debugserver is not aligned to a doubleword boundary. Most of these were fixed in 2017 by Vedant ([MachException] Avoid alignment UB, NFC) but there was a codepath when debugserver logging is enabled where we would still access the mach exception data without aligning it first. This has been causing failures on the sanitizer greendragon bot for the last few days from Jim's change in https://reviews.llvm.org/D157556 where he is enabling LOG_EXCEPTIONS debugserver logging unconditionally (this should prob be in a self.TraceOn() conditional, or maybe not even be in the test - it looks like a debug print he forgot to remove) in the new test_shadow_listener test.
Simplest fix, and it's only done when LOG_EXCEPTIONS is enabled, is to align the data one-off for the logging.
I would have handed this to Jim to fix, but by the time I understood what the actual failure was, it was nothing to fix it.