[Top][All Lists]

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

minibuffer-message segfault

From: Thomas R. Shannon
Subject: minibuffer-message segfault
Date: Fri, 24 Jan 2003 17:40:21 GMT
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

In GNU Emacs 21.2.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-08-28 on astest
configured using `configure  --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu 
--target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr 
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc 
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib 
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com 
--mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop 
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: en_US
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

1. Start an xterm (rxvt).
2. Type "emacs" at the command prompt to start Emacs.
3. Type the following in the *scratch* buffer:

        (minibuffer-message nil)

4. Evaluate the command with M-x eval-region

5. Emacs fails (i.e. the program stops running and Emacs disappears
   from the display).  The following error message appears in the
   terminal followed by the new command prompt:

   Fatal error (11).Segmentation fault

Emacs should handle this error without segfaulting.

My system is a standard Red Hat 8.0 install with no relevant
modifications to emacs.  The following command under the same
circumstances clears the minibuffer with no errors:

     (minibuffer-message "")

Good luck,
Tom Shannon

Quote of the Day for Friday, January 24, 2003
The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer
professionals. We cause accidents.
            -- Nathaniel Borenstein

reply via email to

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