Hi Ken,

On Jul 14 15:09, Ken Brown wrote:
> On 7/3/2015 9:09 AM, Ken Brown wrote:
> >I think I found the cause of that second SIGSEGV, and, if I'm right, it
> >has nothing to do with Cygwin.  I think the problem was that in my
> >testing, I forgot to reset max-specpdl-size and max-lisp-eval-depth to
> >reasonable values after the recovery from stack overflow.  If I do that,
> >then I can no longer reproduce the crash.
> 
> Just for the sake of the archives, it turned out that I could reproduce that
> second crash after all.  But it was an emacs bug, which has now been fixed:
> 
>   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20996
> 
> So there are no loose ends; everything I know how to test involving the
> alternate stack works.

Nice to know, thanks a lot.  I'm planning to release 2.1.0 tomorrow if
nothing gets in the way.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgp36v2pEmqm9.pgp
Description: PGP signature

Reply via email to