Attention is currently required from: Maximilian Brune.
1 comment:
File src/arch/arm64/armv8/exception.c:
if (idx < 10)
__uart_tx_byte('0' + (char)idx);
else if (idx < 16)
__uart_tx_byte('A' - 10 + (char)idx);
__uart_tx_byte('!');
UART_DIRECT_PRINT(raw_read_esr(), 32)
__uart_tx_byte('!');
I may overdid it a bit with this output, so I am open to leave it out if others think it is too much […]
Yeah, honestly, I feel like outputting the arguments is a bit much. In general it's never "supposed" to hang after this, and when it does that's usually only in the cases where you're actively trying to get some new platform to work and can easily inject some more code and try again. It's not hard to write up something like you have here, after all, but I don't think we want to carry it around all the time.
I understand the desire for something that's a bit easier to track down though. "FAIL" still sounds a bit too generic to me? How about something like
```
const char *msg = "\r\n!EXCPT!";
while (*msg)
__uart_tx_byte(*msg++);
```
To view, visit change 80184. To unsubscribe, or for help writing mail filters, visit settings.