Re: [Patch 21.4] native cygwin xemacs-21.4.19 segfaults when requiring un-define
Ar an chéad lá de mí Lúnasa, scríobh Stephen J. Turnbull:
The main concern I have is that Aidan admits that the code hasn't
been
audited for memory leaks, which is always a concern when moving from
alloca (which is effectively garbage-collected by the stack
discipline) to malloc. OTOH, byte-compilation is a very rare event;
any leaks probably will not be noticable.
Probably running a full compile with XEmacs instrumented by valgrind
or similar would catch almost all problems.
Or breaking just after the xnew_array, doing a garbage-collect, and making
sure that the array is now garbage. Avoiding such objects being
garbage-collected is the point of GCPRO, after all.
--
Santa Maradona, priez pour moi!