Can precondition failure exit in a recognizable manner?

[taylorswift]

today, when a Swift program exits due to precondition failure, it prints something like

💣 Program crashed: Illegal instruction at 0x00005d6d19cf4117

this looks a lot like a “corruption” bug (like a misuse of Unmanaged, or one of the known miscompilation modes), so i spent many hours today trying to isolate a suspected refcounting issue instead of realizing this was in fact a precondition failure i had planted myself weeks earlier.

i understand the arguments about printing the error message, which i’ll link here for convenience:

What is the reason for precondition(condition:message:) to fail silently in release builds?

I literally spent 7+ hours debugging crashing web server with 132 exit code. At first I thought it's a swift-docker related problem, but then I found out in stdlib source code (and shortly after that in official documentation, lol) that precondition shows error message only in debug builds, otherwise just trap. I can't come up with any reason to do that, because obviously a) this is what precondition is made for — to do sanity checks not just in debug builds (like assert), but also in release a…

but i feel like it would still be helpful if precondition failures at least indicated they originate from a precondition call, instead of just printing Illegal instruction.

are there reasons why precondition failures can’t identify themselves as precondition failures?