> From: Taahir Ahmed <[email protected]> > Date: Mon, 23 Feb 2015 15:59:43 -0600 > > 2) Replace all uses of set/longjmp with replacements (call them > eh_setjmp and eh_longjmp) that are based on libunwind [1]. > eh_longjmp uses libunwind to walk up the stack, calling each > frame's personality routine [2]. This approach will requires a > platform that uses DWARF exception handling (i.e., everybody > except non-Cygwin Windows).
mingw.org's MinGW uses DWARF exception handling. Perhaps you are thinking of MinGW64, which (AFAIK) indeed uses eh by default, but can be configured to use DWARF. As for libunwind, are you sure it supports enough platforms to be a useful alternative? AFAIK, the last official release supports only IA-64, and even the current development version in git repo basically supports GNU/Linux and almost nothing else (2 FreeBSD targets and 1 on HP-UX).
