Re: libsigsegv error handling

Eric Blake 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 pick

Re: libsigsegv error handling

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Reini Urban on 7/22/2009 2:24 AM: >> 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 stil

Re: libsigsegv error handling (was: perl threads on 2008 R2 64bit)

2009/7/17 Eric Blake: > Dave Korn writes: > >>   That looks fairly robust to me, shouldn't give us any problems.  Question >> is, what does the code that hooks and unhooks the exception handler look >> like, >> and where does it get called from? > > static void > do_install_main_exception_filter (

libsigsegv error handling (was: perl threads on 2008 R2 64bit)

Dave Korn googlemail.com> writes: > That looks fairly robust to me, shouldn't give us any problems. Question > is, what does the code that hooks and unhooks the exception handler look like, > and where does it get called from? static void do_install_main_exception_filter () { /* We cannot i