On 2006-2-7 17:30 UTC, Thomas Tutone wrote:
> Brian Dessent wrote:
>>However, in order to achieve this the DWARF2 unwinder requires
>>cooperation from all the code in the call stack. This leads to issues
>>if your code is ever inside a win32 callback and then throws an
>>exception. (This is quite common in GUI event loops I believe, where
>>your window handler procedure (WinProc) is one large callback.)
> Are there any recent minGW builds using DWARF2
> exception handling? If not, does anyone have recent
> experience doing a native minGW build from sources
> with DWARF2 exception handling enabled?
I think there was one formal release that used dwarf2.
The mailing-list archives would give many details.
> I ask because I have a project in which the sjlj
> performance penalty is severe - it runs 50% slower
> than the same project built using djgpp (which has its
> own issues) on the same system. The project makes
> extensive use of exceptions but does not (because it's
> a console app) throw exceptions from inside a Win32
If I understand it correctly, the problem occurs whenever
a C++ exception crosses a dll boundary, which can happen
in a console app.