Thank you Stephen and Norbert.
I will resubmit the bug with as much detail as possible. I theorized to
a coworker that I believe the problem is more inherent to some system
configuration or limitation on our Unix platform rather then with xemacs
From: Stephen J. Turnbull [mailto:stephen＠xemacs.org]
Sent: Wednesday, April 23, 2008 3:44 PM
To: Norbert Koch
Cc: xemacs-beta(a)xemacs.org; Adam Rappoport
Subject: verilog mode problem
Norbert Koch writes:
> different names then the ports. Anyways I find that at the top
level > > these autos fail and I get a message, buffer to big as xemacs
goes > > through the auto sequence. Is there any remedy to this?
> Any advice or ideas who I may forward this question to would be
> Adam Rappoport
Please report the *exact* message in full. This makes it much easier to
identify the code where the failure is occurring (if it's in XEmacs).
A quick grep through verilog.el gives no hits on "too big". XEmacs
buffers have no size limit (except the amount of virtual memory
available on your system), so it seems likely that this is occuring in a
subprocess (verilog itself?), not in XEmacs.
Please follow up, however. It is possible that XEmacs is configuring
the subprocess with too little memory or something, and that by changing
the configuration of verilog mode this constraint can be relaxed.
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and contains information that is confidential and
proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used
solely for the purpose of furthering the parties' business relationship. All
unauthorized review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy all copies of
the original message.
XEmacs-Beta mailing list