Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 71589 - segfault when following instructions to enable UTF-8
segfault when following instructions to enable UTF-8
Product: Red Hat Public Beta
Classification: Retired
Component: xemacs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2002-08-15 10:12 EDT by Daniel Resare
Modified: 2015-01-07 18:59 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-15 10:14:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
stdout from the xemacs process (3.13 KB, text/plain)
2002-08-15 10:14 EDT, Daniel Resare
no flags Details

  None (edit)
Description Daniel Resare 2002-08-15 10:12:57 EDT
Description of Problem:
When I try to enable utf-8 support in xemacs and follows the instructions in the
file /usr/lib/xemacs/mule-packages/etc/mule-ucs/README.XEmacs
and add 

(require 'un-define)
(set-coding-priority-list '(utf-8))
(set-coding-category-system 'utf-8 'utf-8)

to my $HOME/.xemacs/init.el and open a file with some swedish chars encoded in
utf-8 in i get a really nice segfault.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. Add the above to $HOME/.xemacs/init.el
2. add some non-ascii chars to test.txt with for example 'vim'
3. open test.txt with xemacs

Actual Results:
segfault with nice traceback (attaching)

Additional Information:
I suppose I don't need to say that utf-8 support is nessecary now when the
default locale is utf-8
Comment 1 Daniel Resare 2002-08-15 10:14:13 EDT
Created attachment 70844 [details]
stdout from the xemacs process
Comment 2 Trond Eivind Glomsrxd 2002-08-15 15:33:58 EDT
Fixed in 21.4.8-14

Note You need to log in before you can comment on or make changes to this bug.