GNU bug report logs - #1243
Verilog mode hanging emacs 22.2

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1243 in the body.
You can then email your comments to 1243 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Mitchell, Paul" <Paul.Mitchell <at> amd.com>
To: <bug-gnu-emacs <at> gnu.org>
Subject: Verilog mode hanging emacs 22.2
Date: Fri, 24 Oct 2008 16:38:08 -0400

[Message part 1 (text/plain, inline)]

Hi,

We recently switched from emacs 21.3 to 22.2, and have started seeing
this hang.  I've tried updating verilog-mode.el, but it behaves the same
way.  Emacs 21.3 does not exhibit this.

The symptoms:

Bring a verilog file (*.v) into the editor, and either search for
something or simply page down thru it.  After a few searches or pages,
the clock symbol is displayed on the mouse cursor, and emacs is
completely unresponsive.  A "top" shows that emacs is using most of the
cpu.  Nothing I've tried from within emacs has been able to break out of
this - the emacs process is hung.  This seems to happen more with
font-lock mode enabled, but it also occurs w/o it.

I've contacted the maintainer of verilog-mode, and he has been able to
reproduce this, but is unsure how to debug it.  His stack trace:

(gdb) where
#0  0x08171d01 in Fbyte_code (bytestr=136448595, vector=136448620, 
maxdepth=56) at bytecode.c:508
#1  0x081485e4 in Feval (form=136448581) at eval.c:2334
#2  0x0814a709 in internal_lisp_condition_case (var=137418953, 
bodyform=136448581, handlers=136448805) at eval.c:1426
#3  0x081722e3 in Fbyte_code (bytestr=136448515, vector=136448532, 
maxdepth=32) at bytecode.c:869
#4  0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#5  0x08148e4b in Ffuncall (nargs=1, args=0xbface160) at eval.c:3043
#6  0x081730b9 in Fbyte_code (bytestr=156662779, vector=156663996, 
maxdepth=16) at bytecode.c:679
#7  0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#8  0x08148e4b in Ffuncall (nargs=1, args=0xbface260) at eval.c:3043
#9  0x081730b9 in Fbyte_code (bytestr=156624227, vector=156689996, 
maxdepth=32) at bytecode.c:679
#10 0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#11 0x08148e4b in Ffuncall (nargs=1, args=0xbface360) at eval.c:3043
#12 0x081730b9 in Fbyte_code (bytestr=136448595, vector=136448620, 
maxdepth=56) at bytecode.c:679
#13 0x081485e4 in Feval (form=136448581) at eval.c:2334
#14 0x0814a709 in internal_lisp_condition_case (var=137418953, 
bodyform=136448581, handlers=136448805) at eval.c:1426
#15 0x081722e3 in Fbyte_code (bytestr=136448515, vector=136448532, 
maxdepth=32) at bytecode.c:869
#16 0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#17 0x08148e4b in Ffuncall (nargs=1, args=0xbface660) at eval.c:3043
#18 0x081730b9 in Fbyte_code (bytestr=156662779, vector=156663996, 
maxdepth=16) at bytecode.c:679
#19 0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#20 0x08148e4b in Ffuncall (nargs=1, args=0xbface760) at eval.c:3043
#21 0x081730b9 in Fbyte_code (bytestr=156624227, vector=156689996, 
maxdepth=32) at bytecode.c:679
#22 0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184
#23 0x08148e4b in Ffuncall (nargs=1, args=0xbface860) at eval.c:3043
#24 0x081730b9 in Fbyte_code (bytestr=136448595, vector=136448620, 
maxdepth=56) at bytecode.c:679
#25 0x081485e4 in Feval (form=136448581) at eval.c:2334
#26 0x0814a709 in internal_lisp_condition_case (var=137418953, 
bodyform=136448581, handlers=136448805) at eval.c:1426
#27 0x081722e3 in Fbyte_code (bytestr=136448515, vector=136448532, 
maxdepth=32) at bytecode.c:869
#28 0x081489d5 in funcall_lambda (fun=Variable "fun" is not available.
) at eval.c:3184


The details of my system configuration:

In GNU Emacs 22.2.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2008-04-17 on madccat02
Windowing system distributor `Hummingbird Ltd.', version 11.0.10000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: C
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Major mode: Text

Minor modes in effect:
  shell-dirtrack-mode: t
  display-time-mode: t
  show-paren-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t


Any suggestions for how to proceed with this?  We'd like to stay
reasonably up-to-date with emacs releases, but as we edit verilog all
the time, this is a bit of a showstopper for us.

Thanks,
Paul Mitchell
HW Design Engineer
AMD, Inc.
(508) 303-3932

[Message part 2 (text/html, inline)]

Message #12 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: "Mitchell\, Paul" <Paul.Mitchell <at> amd.com>
Cc: 1243 <at> debbugs.gnu.org, <bug-gnu-emacs <at> gnu.org>
Subject: Re: bug#1243: Verilog mode hanging emacs 22.2
Date: Sat, 25 Oct 2008 14:38:38 -0400

> Bring a verilog file (*.v) into the editor, and either search for
> something or simply page down thru it.  After a few searches or pages,
> the clock symbol is displayed on the mouse cursor, and emacs is
> completely unresponsive.  A "top" shows that emacs is using most of the
> cpu.  Nothing I've tried from within emacs has been able to break out of
> this - the emacs process is hung.  This seems to happen more with
> font-lock mode enabled, but it also occurs w/o it.

> I've contacted the maintainer of verilog-mode, and he has been able to
> reproduce this, but is unsure how to debug it.  His stack trace:

To make better sense of the stack trace, you need to use `xbacktrace'
(which will give a Lisp-level interpretation of the stack).
`xbacktrace' is defined in emacs/src/.gdbinit so you need to start `gdb'
from the `src' directory of the Emacs build tree.


        Stefan

Message #22 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Mitchell, Paul" <Paul.Mitchell <at> amd.com>
To: "Stefan Monnier" <monnier <at> iro.umontreal.ca>
Cc: <1243 <at> debbugs.gnu.org>, <bug-gnu-emacs <at> gnu.org>,
        "Bilik, Scott" <Scott.Bilik <at> amd.com>
Subject: RE: bug#1243: Verilog mode hanging emacs 22.2
Date: Mon, 27 Oct 2008 09:58:05 -0400

Stefan,

I ran emacs under gdb, from within the src directory.  I then edited the
file that exhibits this problem and did a few incremental searches.
This caused emacs to hang.  I tried to break out of this from gdb using
ctrl-c, which killed emacs so that I could not use xbacktrace.  Then,
from the gdb prompt I used: "handle SIGINT stop", got back to the hang,
and tried ctrl-c again.  I now was able to use xbacktrace, and see this:


(gdb) xbacktrace
"re-search-backward" (0x86f1eeb)
"verilog-beg-of-defun" (0x87cfd85)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8811595)
"verilog-beg-of-defun" (0x87cfd85)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8804edd)
"verilog-beg-of-defun" (0x87d1405)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8804e9d)
"verilog-beg-of-defun" (0x87d1405)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8808745)
"verilog-beg-of-defun" (0x87d1405)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8808785)
"verilog-beg-of-defun" (0x87d1405)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x88087c5)
"verilog-beg-of-defun" (0x87dabdd)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x87edc35)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711c85)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711cf5)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711d35)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711d75)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711dd5)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711e65)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711f15)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
---Type <return> to continue, or q <return> to quit---
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711f55)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x8711f95)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x871203d)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"verilog-syntax-ppss" (0x831e8c9)
"verilog-skip-backward-comment-or-string" (0x87120b5)
"verilog-beg-of-defun" (0xa4670)
"byte-code" (0x8234d13)
"syntax-ppss" (0x1122c8)
"font-lock-fontify-syntactically-region" (0x1122c8)
"font-lock-default-fontify-region" (0x1122c8)
"font-lock-fontify-region" (0x1122c8)
"run-hook-with-args" (0x8514ce1)
"byte-code" (0x8239e2b)
"jit-lock-fontify-now" (0x112458)
"jit-lock-function" (0x112458)
(gdb)  

-----Original Message-----
From: Stefan Monnier [mailto:monnier <at> iro.umontreal.ca] 
Sent: Saturday, October 25, 2008 2:39 PM
To: Mitchell, Paul
Cc: 1243 <at> debbugs.gnu.org; bug-gnu-emacs <at> gnu.org
Subject: Re: bug#1243: Verilog mode hanging emacs 22.2

> Bring a verilog file (*.v) into the editor, and either search for
> something or simply page down thru it.  After a few searches or pages,
> the clock symbol is displayed on the mouse cursor, and emacs is
> completely unresponsive.  A "top" shows that emacs is using most of
the
> cpu.  Nothing I've tried from within emacs has been able to break out
of
> this - the emacs process is hung.  This seems to happen more with
> font-lock mode enabled, but it also occurs w/o it.

> I've contacted the maintainer of verilog-mode, and he has been able to
> reproduce this, but is unsure how to debug it.  His stack trace:

To make better sense of the stack trace, you need to use `xbacktrace'
(which will give a Lisp-level interpretation of the stack).
`xbacktrace' is defined in emacs/src/.gdbinit so you need to start `gdb'
from the `src' directory of the Emacs build tree.


        Stefan

Message #32 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: "Mitchell\, Paul" <Paul.Mitchell <at> amd.com>
Cc: <1243 <at> debbugs.gnu.org>, <bug-gnu-emacs <at> gnu.org>,
        "Bilik\, Scott" <Scott.Bilik <at> amd.com>,
        Wilson Snyder
	<wsnyder <at> wsnyder.org>
Subject: Re: bug#1243: Verilog mode hanging emacs 22.2
Date: Mon, 27 Oct 2008 10:20:38 -0400

> I ran emacs under gdb, from within the src directory.  I then edited the
> file that exhibits this problem and did a few incremental searches.
> This caused emacs to hang.  I tried to break out of this from gdb using
> ctrl-c, which killed emacs so that I could not use xbacktrace.  Then,
> from the gdb prompt I used: "handle SIGINT stop", got back to the hang,
> and tried ctrl-c again.  I now was able to use xbacktrace, and see this:

> (gdb) xbacktrace
> "re-search-backward" (0x86f1eeb)
> "verilog-beg-of-defun" (0x87cfd85)
> "byte-code" (0x8234d13)
> "verilog-syntax-ppss" (0x831e8c9)
> "verilog-skip-backward-comment-or-string" (0x8811595)
> "verilog-beg-of-defun" (0x87cfd85)
> "byte-code" (0x8234d13)
> "verilog-syntax-ppss" (0x831e8c9)

I believe the patch below will fix it.  Wilson, WDYT?


        Stefan


--- verilog-mode.el.~1.24.~	2008-09-12 12:39:48.000000000 -0400
+++ verilog-mode.el	2008-10-27 10:18:58.000000000 -0400
@@ -2373,6 +2373,8 @@
 		   ;; Fontify things in translate off regions
 		   '(verilog-match-translate-off
                      (0 'verilog-font-lock-translate-off-face prepend))))))
+  ;; FIXME: This XEmacs setting is redundant with the setting done later
+  ;; for Emacs (because XEmacs obeys's Emacs setting as well).
   (put 'verilog-mode 'font-lock-defaults
        '((verilog-font-lock-keywords
 	  verilog-font-lock-keywords-1
@@ -2560,10 +2562,17 @@
 
   ;; Stuff for GNU Emacs
   (set (make-local-variable 'font-lock-defaults)
-       '((verilog-font-lock-keywords verilog-font-lock-keywords-1
+       `((verilog-font-lock-keywords verilog-font-lock-keywords-1
                                      verilog-font-lock-keywords-2
                                      verilog-font-lock-keywords-3)
-         nil nil nil verilog-beg-of-defun))
+         nil nil nil
+         ,(if (functionp 'syntax-ppss)
+              ;; verilog-beg-of-defun uses syntax-ppss, and syntax-ppss uses
+              ;; font-lock-beginning-of-syntax-function, so
+              ;; font-lock-beginning-of-syntax-function, can't use
+              ;; verilog-beg-of-defun.
+              nil
+            verilog-beg-of-defun)))
   ;;------------------------------------------------------------
   ;; now hook in 'verilog-colorize-include-files (eldo-mode.el&spice-mode.el)
   ;; all buffer local:

Message #42 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Mitchell, Paul" <Paul.Mitchell <at> amd.com>
To: "Stefan Monnier" <monnier <at> iro.umontreal.ca>
Cc: <1243 <at> debbugs.gnu.org>, <bug-gnu-emacs <at> gnu.org>,
        "Bilik, Scott" <Scott.Bilik <at> amd.com>,
        "Wilson Snyder" <wsnyder <at> wsnyder.org>
Subject: RE: bug#1243: Verilog mode hanging emacs 22.2
Date: Mon, 27 Oct 2008 10:38:13 -0400

Stefan,

I ran this against my test case just now and emacs no longer hangs.  I'm
moving back to version 22, and will let you know if I see this again,
but it seems fixed.

Thanks for your help,
Paul

-----Original Message-----
From: Stefan Monnier [mailto:monnier <at> iro.umontreal.ca] 
Sent: Monday, October 27, 2008 10:21 AM
To: Mitchell, Paul
Cc: 1243 <at> debbugs.gnu.org; bug-gnu-emacs <at> gnu.org; Bilik,
Scott; Wilson Snyder
Subject: Re: bug#1243: Verilog mode hanging emacs 22.2

> I ran emacs under gdb, from within the src directory.  I then edited
the
> file that exhibits this problem and did a few incremental searches.
> This caused emacs to hang.  I tried to break out of this from gdb
using
> ctrl-c, which killed emacs so that I could not use xbacktrace.  Then,
> from the gdb prompt I used: "handle SIGINT stop", got back to the
hang,
> and tried ctrl-c again.  I now was able to use xbacktrace, and see
this:

> (gdb) xbacktrace
> "re-search-backward" (0x86f1eeb)
> "verilog-beg-of-defun" (0x87cfd85)
> "byte-code" (0x8234d13)
> "verilog-syntax-ppss" (0x831e8c9)
> "verilog-skip-backward-comment-or-string" (0x8811595)
> "verilog-beg-of-defun" (0x87cfd85)
> "byte-code" (0x8234d13)
> "verilog-syntax-ppss" (0x831e8c9)

I believe the patch below will fix it.  Wilson, WDYT?


        Stefan


--- verilog-mode.el.~1.24.~	2008-09-12 12:39:48.000000000 -0400
+++ verilog-mode.el	2008-10-27 10:18:58.000000000 -0400
@@ -2373,6 +2373,8 @@
 		   ;; Fontify things in translate off regions
 		   '(verilog-match-translate-off
                      (0 'verilog-font-lock-translate-off-face
prepend))))))
+  ;; FIXME: This XEmacs setting is redundant with the setting done
later
+  ;; for Emacs (because XEmacs obeys's Emacs setting as well).
   (put 'verilog-mode 'font-lock-defaults
        '((verilog-font-lock-keywords
 	  verilog-font-lock-keywords-1
@@ -2560,10 +2562,17 @@
 
   ;; Stuff for GNU Emacs
   (set (make-local-variable 'font-lock-defaults)
-       '((verilog-font-lock-keywords verilog-font-lock-keywords-1
+       `((verilog-font-lock-keywords verilog-font-lock-keywords-1
                                      verilog-font-lock-keywords-2
                                      verilog-font-lock-keywords-3)
-         nil nil nil verilog-beg-of-defun))
+         nil nil nil
+         ,(if (functionp 'syntax-ppss)
+              ;; verilog-beg-of-defun uses syntax-ppss, and syntax-ppss
uses
+              ;; font-lock-beginning-of-syntax-function, so
+              ;; font-lock-beginning-of-syntax-function, can't use
+              ;; verilog-beg-of-defun.
+              nil
+            verilog-beg-of-defun)))
   ;;------------------------------------------------------------
   ;; now hook in 'verilog-colorize-include-files
(eldo-mode.el&spice-mode.el)
   ;; all buffer local:

Message #54 received at 1243-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 1243-done <at> debbugs.gnu.org
Subject: Re: bug#1243: Verilog mode hanging emacs 22.2
Date: Thu, 12 Feb 2009 23:09:17 -0500

2009-02-12  Stefan Monnier  <monnier <at> iro.umontreal.ca>

    * progmodes/verilog-mode.el (verilog-mode): Avoid circular use of
    syntax-ppss.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.