Message GDB when rr crashes/assertion fails

I'm not sure if this is functionality that can be implemented (or if it's just something that can be chalked up to the unstable nature of the AMD support), but it seems as though GDB is unaware of when rr fails due to an assertion failing.

Could it be possible to implement some feature to signal GDB when rr fails? It doesn't seem to matter what kind of assertion it is that fails, but when it does (in this case, for this issue an assertion failed due to tick inconsistency) GDB just "cruises along" or rather, just hangs indefinitely, thinking the inferior is running.

Perhaps there is some error message/packet that can be sent using the GDB Server Protocol (which if I'm not mistaken is what rr uses to communicate with GDB?) prior to spitting out the backtrace? Maybe setup a signal handler somehow and send it from there is possible? I'm just speculating wildly about solutions here, seeing as how I literally have no clue how the communication works, but if there is some kind of functionality resembling this, I'd be glad to give it a go of looking into.

Start by tracing rr's communication with GDB through the GDB Server Protocol and how assertion failures or crashes are handled. Determine whether an error packet or signal can report the failure; done means GDB no longer remains in a running state or hangs when rr encounters an assertion failure.