Re: Bug triggered by compilation-mode + font-lock, XEmacs 21.4.11.
Vin,
'ulimit -a' shows a stack size of 8192.
Specifying 'unlimited' did NOT help.
Removing "#define REGEX_MALLOC 1" from src/config.h DID help.
So what does this tell us?
I don't have any new packages other than what was part of the new sumo. The
new hyperbole and oo-browser packages, introduced with the new sumo, were
already part of my xemacs-packages anyway.
Is there anything else I can do to help with this problem or is this already
an understood issue?
...Jake
>>>> "VS" == Vin Shelton <acs(a)xemacs.org>
writes:
VS> Jake Colman <jake.colman(a)xemacs.org> writes:
> I am getting a "Stack overflow in regexp matcher" in
21.4.14 when
> trying to use a compilation-mode buffer. The error is triggered
> when doing a `C-C C-c' or a `C-x `'. I do NOT have this problem
> with 21.4.13. Is this related to what's being discussed in this
> thread? If so, what do I do about it?
VS> Yours was the case that prompted me to ask for confirmation, yes.
VS> Please check your generated src/config.h file to see if REGEX_MALLOC
VS> is defined. It should be:
VS> #define REGEX_MALLOC 1
VS> for 21.4.14. Assuming this is correct, you could try commenting out
VS> that definition to see if that helps. (This would take you back to
VS> the default 21.4.13 behavior.)
VS> What does the "ulimit -a" command say is your stack size? My guess
is
VS> that a new package is causing you problems with your regexp and that
VS> you are blowing through your stack limit. In theory,
VS> #define REGEX_MALLOC 1
VS> should help in this case, but only if your stacksize is large.
VS> First I would try running the command
VS> ulimit -s unlimited
VS> before running XEmacs.
VS> Then second I would try uncommenting the REGEX_MALLOC definition.
VS> Finally, I would do the package fiddling you described in another
VS> email.
VS> HTH,
VS> Vin
--
Jake Colman -- XEmacs Tinkerer