home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.emacs.bug
- Path: sparky!uunet!convex!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!epilogue.com!sra
- From: sra@epilogue.com (Rob Austein)
- Subject: invalid buffer-file-name crashes emacs
- Message-ID: <9208130421.aa03333@quern.epilogue.com>
- Sender: gnulists@ai.mit.edu
- Organization: GNUs Not Usenet
- References: sra@epilogue.com (Rob Austein)
- Distribution: gnu
- Date: Thu, 13 Aug 1992 08:21:31 GMT
- Approved: bug-gnu-emacs@prep.ai.mit.edu
- Lines: 21
-
- Date: 12 Aug 92 21:42:01 GMT
- From: dan@uiucmath.math.uiuc.edu (Daniel R. Grayson)
-
- Do this to make emacs 18.58 crash with an illegal instruction on a
- vaxstation II running Ultrix 2.0.
-
- (find-file "junk.foo")
- (setq buffer-file-name (cons "asdf" "qwer"))
- (insert "asdf")
-
- The function lock_file() [$EMACS/src/filelock.c] takes a Lisp_Object
- as the name of the file to lock. It assumes that this Lisp_Object is
- a string but does not check to be certain. In your example, this
- results in attempting to use some random portion of cons space as a
- null terminated C string, with predictable results.
-
- lock_file() should do a CHECK_STRING() on its argument so that emacs
- can signal an error and carry on rather than dumping core.
-
- --Rob Austein <sra@epilogue.com>
-
-