Bug 107402
Summary: | Stack overflow in regexp matcher | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rik Faith <faith> |
Component: | xemacs | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-11-18 08:24:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rik Faith
2003-10-17 19:30:07 UTC
Here is a more recent bug report and patch: http://list-archive.xemacs.org/xemacs-beta/200309/msg00205.html Thanks for the report. Applying the above patch in xemacs-21.4.13-3. 21.4.14-3 even As for the build problems you are having 21.4.14-2 and later no longer need %_prefix/X11R6/lib/X11/ so that problem should be gone. So the built xemacs can't find any elisp files? I think you need xemacs-sumo installed. I have tested -3, and it C-x ` works for a much larger range of programs. However, I still see a stack overflow at times. I have added the following lines to the xemacs.spec file after the %patch20 line and this seems to help: cp -p src/regex.c src/regex.c.rik sed 's,int re_max_failures = 20000;,int re_max_failures = 40000;,' \ < src/regex.c.rik > src/regex.c However, I haven't seen any postings suggesting this will be an upstream fix. [Also, the build problems seem to be resolved ASSUMING I build xemacs-sumo.spec before xemacs-spec, and they have version numbers that match. I believe this is expected behavior.] Using 40000, 4000 in xemacs-21.4.14-4. [Not sure what you mean by "version numbers that match"?] Sorry for not being clear. If I build and install xemacs.spec and xemacs-sumo.spec simultaneously, xemacs will only be able to find its startup files if the Version AND Release lines are identical in the two *.spec files. (This is a change from pre-RH9, for example, where I was able to bump just the Release on the xemacs.spec file and have it work with whatever other xemacs packages were installed.)> I'm probably overlooking something obvious, but how can the version numbers of xemacs and xemacs-sumo be the same? Sorry, I misspoke. I thought that the Release (not Version) numbers had to be the same. But that's wrong too. Please ignore comment #8. The problem was that the hardcoded paths in sitestart.el assumed a full installation in /usr, and I was building xemacs to install in /usr/local. I have corrected this problem and can now build a one-off xemacs package that relies on the standard Fedora xemacs-sumo package. |