Eric Blake <ebb9 <at> byu.net> writes: > >> Is there a chance that this represents a bug in > >> libsigsegv SEH handling that needs to be reported upstream? > > > > I'll report that, if it turns out so. > > I've already mentioned it to Bruno, and am still working on a fix.
FWIW, rebuilding m4 1.4.13 picks up the new libsigsegv0 dll, but it still exhibits the crash when used under cygwin-1.7.0-51 (ie. the bug is not whether libsigsegv was linked in static or dynamic, but that libsigsegv is over-eager to claim that all SEH faults should be handled like SEGV faults). The particular m4 crash is gone with cygwin1.dll built today (thanks to my recent newlib fflush patch). Meanwhile, I will be packaging m4-1.4.13-2 to pick up the new libsigsegv0 (so that when Bruno does fix libsigsegv, I don't have to rebuild m4-1.4.13-3 to relink against the fix), and that will also include a one-liner patch (currently in m4.git) that makes the particular m4 crash go away even if you don't have a self-built cygwin1.dll. -- Eric Blake -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
