From xemacs-m  Thu Mar 13 10:41:17 1997
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA00648
	for <xemacs-beta@xemacs.org>; Thu, 13 Mar 1997 10:41:15 -0600 (CST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.8.5/8.8.5) with ESMTP id LAA20796;
	Thu, 13 Mar 1997 11:40:43 -0500
Message-Id: <199703131640.LAA20796@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Steven L Baur <steve@miranova.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: locale 
In-Reply-To: Your message of "12 Mar 1997 20:09:44 PST."
             <m2wwrc1lh3.fsf@altair.xemacs.org> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
References: <199703130349.VAA04503@mharnois.workgroup.net>
            <m2wwrc1lh3.fsf@altair.xemacs.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1106868078P";
	micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Mar 1997 11:40:42 -0500

--==_Exmh_1106868078P
Content-Type: text/plain; charset=us-ascii

On 12 Mar 1997 20:09:44 PST, you said:
> Michael Harnois writes:
> 
> > Oooh. It says it when I start xemacs, too.
> 
> It's coming from XEmacs XIM code.  Putting LANG=C in your environment
> might make the message go away.  It would probably be better to find
> out why the call to setlocale(LC_ALL, "") is failing.

FWIW, I was just trying to play with the XIM support the other day, and
got into a major horrorshow on AIX 4.2.  To Wit:

When running with the locale set to C, or en_US, or Lv_LV (which
are ASCII, ISO8859-1, and ISO8859-4 based, respectiviely), all worked
pretty much as expected (although I admit I did *NOT* do any testing on
composing/inputting any characters in the top half of 8859-4).

Running with LV_LV however, flamed it out spectacularly.  LV_LV is
apparently a UTF-8 based locale.  Now, I *know* that I'd be massively
surprised if it *worked*, but I must admit being equally surprised at
just how *hard* it took the SIGSEGV (like.. I expected gdb to *catch*
it ;)

I'll follow up eventually, once I manage to beat the debugger into
submission (gdb did better than IBM's dbx, which *itself* SEGV'ed while
trying to read the xemacs module in).

/Valdis 

Script started on Thu Mar 13 10:42:25 1997
[~/src/xemacs-20.1-b5/src/src]2 gdb ./xemacs
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (powerpc-ibm-aix4.1.4.0), 
Copyright 1996 Free Software Foundation, Inc...
(gdb) set environment LANG LV_LV
(gdb) set args "-q"
(gdb) break initial_command_loop
Breakpoint 1 at 0x105531c8: file cmdloop.c, line 243.
(gdb) run
Starting program: /home/spd/valdis/src/xemacs-20.1-b5/src/src/./xemacs "-q"

Breakpoint 1, initial_command_loop (load_me=270516228) at cmdloop.c:243
243	  if (!NILP (load_me))
(gdb) handle SIGSEGV stop nopass
Signal        Stop	Print	Pass to program	Description
SIGSEGV       Yes	Yes	No		Segmentation fault
(gdb) continue
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) [~/src/xemacs-20.1-b5/src/src]2 exit

script done on Thu Mar 13 10:49:21 1997



--==_Exmh_1106868078P
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBMyguCNQBOOoptg9JAQFRfAP+J7ihmkqz6jU8iUqFxMTAhjl4mqfURo0W
DgGmg5ew29Zf/07ylW8bwp4A6CLHwiMoMy0XI3u0oedseuKFzYbyFi2SuUWEIWj9
m9yBzDYT3VfEqPlB0HwyNasr8GphESPkYlgbmrQl0yuu4GhAw8rrwLE1Ol5yP2VK
N6nw7xAOw8o=
=i6X6
-----END PGP MESSAGE-----

--==_Exmh_1106868078P--

