Satheesh> Hi All Satheesh> I've been having some problems with my xemacs (20.4) Satheesh> running on HP-UX Satheesh> 11.00 recently. When I click on the compilation errors Satheesh> using my mouse Satheesh> middle button, it used to take me to the location of the Satheesh> error in the C++ file. Now, I'm getting this error that Satheesh> says: Stack overflow in regexp matcher. Any help with Satheesh> this issue will be greatly appreciated. Hello Satheesh! If necessary/possible, please install the latest net-utils package (>= 1.23) and then use Help->Send Bug Report... or M-x report-emacs-bug as suggested in http://www.xemacs.org/Debug/index.html This will tell us enough about your XEmacs installation so that we should be able to help you. Best regards, Adrian Satheesh> Thanks Satheesh> Satheesh Satheesh> PS: The backtrace of the error in Xemacs is as follows: Satheesh> Signaling: (error "Stack overflow in regexp matcher") Satheesh> looking-at("\\([^\n]*: Entering directory Satheesh> `\\([^\n]*\\)'$\\)\\|\\([^\n]*: Leaving directory Satheesh> `\\([^\n]*\\)'$\\)\\|\\(\\(\\([a-zA-Z]?:?[^:( \n]+\\)[:(][ Satheesh> ]*\\([0-9]+\\)\\([) Satheesh> ]\\|:\\([^0-9\n]\\|\\([0-9]+:\\)\\)\\)\\)\\|\\(\\(\\([a-zA-Z]:\\)?[^:( Satheesh> \n-]+\\)[:(][ ]*\\([0-9]+\\)[:) Satheesh> ]\\)\\|\\(\\(Error\\|Warning\\) \\([a-zA-Z]?:?[^:( \n]+\\) Satheesh> \\([0-9]+\\)\\([) ]\\|:[^0-9\n]\\)\\)\\|\\([^\n]*[ Satheesh> :]\\([a-zA-Z]?:?[^:( \n]+\\)[:(](+[ ]*\\([0-9]+\\))[:) Satheesh> ]*$\\)\\|\\([^\n]*([ ]*\\([a-zA-Z]?:?[^:( \n]+\\)[:(][ Satheesh> ]*\\([0-9]+\\))\\)\\|\\([^ \n]+ (\\([0-9]+\\)) in \\([^ Satheesh> \n]+\\)\\)\\|\\([^\n]*in Satheesh> \\([^(\n]+\\)(\\([0-9]+\\))$\\)\\|\\(\\(cfe\\|fort\\): [^:\n]*: \\([^ Satheesh> \n]*\\), line \\([0-9]+\\):\\)\\|\\(\\(\\|[^\n]* on \\)[Ll]ine[ Satheesh> ]+\\([0-9]+\\)[ ]+of[ Satheesh> ]+\"?\\([a-zA-Z]?:?[^\":\n]+\\)\"?:\\)\\|\\([^\n]*\"\\([^,\" \n Satheesh> ]+\\)\", lines? \\([0-9]+\\)\\([(.]\\([0-9]+\\))?\\)?[:., Satheesh> (-]\\)\\|\\([^\n]*rror: \\([^,\" \n ]+\\)[,:] \\(line Satheesh> \\)?\\([0-9]+\\):\\)\\|\\([^\n]*in line \\([0-9]+\\) of file \\([^ Satheesh> \n]+[^. \n]\\)\\.? \\)\\|\\([EW], \\([^(\n]*\\)(\\([0-9]+\\),[ Satheesh> ]*\\([0-9]+\\)\\)\\|\\([a-zA-Z]?:?[^0-9 Satheesh> \n :]+:[ ]*\\([^ \n :]+\\):\\([0-9]+\\):\\(\\([0-9]+\\)[: Satheesh> ]\\)?\\)\\|\\([^0-9 \n :]+:[ ]*\\([^ \n Satheesh> :]+\\):\\([0-9]+\\):\\(\\([0-9]+\\):\\)?[A-Za-z]:\\)\\|\\([^\n]* \\([^ Satheesh> \n,\"]+\\), line \\([0-9]+\\):\\)\\|\\([^\n]*: \\([^ \n,\"]+\\): Satheesh> \\([0-9]+\\):\\)\\|\\(\\(cc\\| cft\\)-[0-9]+ c\\(c\\|f77\\): ERROR Satheesh> \\([^,\n]+, \\)* File = \\([^,\n]+\\), Line = Satheesh> \\([0-9]+\\)\\)\\|\\(\\([^( \n ]+\\)(\\([0-9]+\\):\\([0-9]+\\)) : Satheesh> \\)\\|\\(\\([^, \n ]+\\), line \\([0-9]+\\), char Satheesh> \\([0-9]+\\)[:., (-]\\)\\)") Satheesh> compilation-parse-errors(9064 nil) Satheesh> byte-code("q¨ Âa¬£ Satheesh> «£Ä ¨ ­³ Satheesh> «¦ Satheesh> V­ª?®¥ GY?­¾È!© «§Ê !¨ª¤Ë!¨)ÌÍ!¨dW­   Satheesh> ­¥ GZ\"¨ ¤­¤©)§" [compilation-last-buffer Satheesh> compilation-error-list t reparse compilation-forget-errors Satheesh> limit-search compilation-parsing-end find-at-least get-buffer-window w Satheesh> select-window switch-to-buffer set-buffer-modified-p nil Satheesh> error-list-pos compilation-parse-errors-function Satheesh> compilation-old-error-list] 5) Satheesh> compile-reinitialize-errors(nil 9064) Satheesh> compile-goto-error() Satheesh> compile-mouse-goto-error(#<buttondown-event button2>) Satheesh> call-interactively(compile-mouse-goto-error) Satheesh> _________________________________________________________________ Satheesh> Send and receive Hotmail on your mobile device: http://mobile.msn.com -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

"Stephen J. Turnbull" <stephen(a)xemacs.org&gt; wrote: Yes, definitely. XEmacs 20.4 is *REALLY* ancient .... I do, unfortunately. ;-( No, no, no. ;-) Different problem (mostly ;-). This particular message is being caused by the fact that the value of re_max_failures in src/regex.c is too small. The default value is 2000 (for HP-UX, at least, because MATCH_MAY_ALLOCATE is not #define'd), and bumping the value up makes the problem go away. When I compile XEmacs, I usually change the default value to 20000. However, by kicking up re_max_failures, you will probably need the stack limit to be increased (or XEmacs can intermittently core dump), which requires a kernel rebuild for HP-UX. I don't know what the default max stack limit is for HP-UX 11.00, but it used to be 2MB for HP-UX 10.20. With re_max_failures set to 20000, a max stack size of 16MB worked for me. -- Darryl Okahata darrylo(a)soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day.