Alastair Houghton 143a473aa4 [Runtime][IRGen] Trap C++ exceptions on *throw*, not catch. ...

The previous approach was effectively to catch the exception and then
run a trap instruction.  That has the unfortunate feature that we end
up with a crash at the catch site, not at the throw site, which leaves
us with very little information about which exception was thrown or
where from.

(Strictly we do have the exception pointer and could obtain exception
information, but it still won't tell us what threw it.)

Instead of that, set a personality function for Swift functions that
call potentially throwing code, and have that personality function
trap the exception during phase 1 (i.e. *before* the original stack
has been unwound).

rdar://120952971

2024-02-06 16:19:17 +00:00

1.5 KiB

Raw Permalink Blame History

View Raw