Yoshiki Hayashi <yoshiki(a)xemacs.org> writes:
Matt Tucker <tuck(a)whistlingfish.net> writes:
> -- Martin Buchholz <martin(a)xemacs.org> spake thusly:
>
> > For bonus points: write a program that will find all the places in
> > the code that a naked return (without RETURN_UNGCPRO) is being called
> > from within a GCPRO'ed region of code.
>
> Not sure if this is what you want, but I hacked together a
> quick Perl script which probably comes close (although it
> finds a bunch of stuff in comments as well as bits you
> actually care about):
Thanks! Here's the fix.
[...]
I'm impressed. This fixes at least several possible causes of nasty
crashes. This patch once again shows that GCPRO, while it may be a
superior implementation technique, is not made for a human mind to get
right.