8:18 p.m.
core dump in XtDestroyWidget() on HPUX 10.20
I have seen XEmacs core dump while taking dialog boxes down. Specifically,
when a dialog box is completed with a manual entry and a carraige return,
such as File => Save As... type the name and press enter. This does not
seem to happen when mouse selecting OK. It doesn't always happen on the
first try, but I can reliably reproduce this by the third or fourt try.
I'll try to include all relaveent information.
I have reproduced this error on the following versions 20.4, 21.0.67,
and 21.1.2. The included data is from 21.1.2. Version 20.2 DOES NOT
express the error.
What else should be included to make this report complete?
dsm(a)fc.hp.com
Xemacs version 21.1.2 expresses a core dump under the following conditions:
HPUX 10.20 in Japanese SJIS mode
$LANG=ja_JP.SJIS
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
configure options
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
./configure hppa1.1-hp-hpux10.20 \
--extra-verbose \
--compiler="/opt/ansic/bin/cc" \
--x-includes="/usr/include/X11R6 -I/usr/include/Motif1.2_R6" \
--x-libraries="/usr/lib/X11R6 -L/usr/lib/Motif1.2_R6" \
--error-checking=none \
--dynamic=no \
--with-x11=yes \
--with-menubars=lucid \
--with-scrollbars=motif \
--with-dialogs=motif \
--with-xmu=no \
--with-xim \
--with-mule=yes \
--with-cde=yes \
--debug \
--cflags="+DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Ovectorize
+Ofastaccess
+Oprocelim"
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.emacs contents
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
(set-language-environment 'Japanese)
(set-pathname-coding-system 'shift_jis-unix)
(set-default-buffer-file-coding-system 'shift_jis)
(set-buffer-file-coding-system-for-read 'shift_jis)
(set-keyboard-coding-system 'shift_jis)
(set-terminal-coding-system 'shift_jis)
(set-default-coding-systems 'shift_jis)
;; I can reproduce the core with NO .emacs file
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
core dump runtime output (machine named hellcat)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
hellcat, (10:27)> ./xemacs
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Please report this bug by running the send-pr script included
with XEmacs, or selecting `Send Bug Report' from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb
/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-21.1.2/src/xemacs
core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
kill-emacs()
# bind (arg)
save-buffers-kill-emacs(nil)
# bind (command-debug-status)
call-interactively(save-buffers-kill-emacs)
# (condition-case ... . error)
# (catch top-level ...)
Memory fault(coredump)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
gdb backtrace
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
hellcat, (10:42)> /nfs/zappa/usr/local/bin/gdb
/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-21.1.2/src/xemacs core
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "hppa1.1-hp-hpux10.20"...(no debugging symbols
found)...
Core was generated by `xemacs'.
Program terminated with signal 11, Segmentation fault.
warning: The shared libraries were not privately mapped; setting a
breakpoint in a shared library will not work until you rerun the program.
Reading symbols from ./xemacs...(no debugging symbols found)...done.
Reading symbols from /usr/dt/lib/libXm.1...(no debugging symbols
found)...done.
Reading symbols from /usr/dt/lib/libDtSvc.1...(no debugging symbols
found)...done.
Reading symbols from /usr/dt/lib/libtt.1...(no debugging symbols
found)...done.
Reading symbols from /usr/dt/lib/libXt.1...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/X11R6/libXext.2...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/X11R6/libX11.2...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/X11R6/libSM.1...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/X11R6/libICE.1...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/libc.1...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libdld.sl...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/nls/loc/locales.1//ja_JP.SJIS...(no debugging
symbols
found)...done.
Reading symbols from /usr/lib/nls/loc/methods/libSJIS.sl...(no debugging
symbols
found)...done.
#0 0xc0137598 in kill ()
(gdb) where
#0 0xc0137598 in kill ()
#1 0x85850 in fatal_error_signal ()
#2 <signal handler called>
#3 0xc177da00 in _XimProtoKeypressFilter ()
#4 0xc177db24 in _XimFilterKeypress ()
#5 0xc174db58 in XFilterEvent ()
#6 0xc13248b4 in DispatchEvent ()
#7 0xc132553c in DecideToDispatch ()
#8 0xc1325624 in XtDispatchEvent ()
#9 0xc14bc5c4 in RemoveAllPMgr ()
#10 0xc13190fc in XtCallCallbackList ()
#11 0xc1320dd0 in Phase2Callbacks ()
#12 0xc1320d3c in Recursive ()
#13 0xc132113c in XtPhase2Destroy ()
#14 0xc1321300 in _XtDoPhase2Destroy ()
#15 0xc1321484 in XtDestroyWidget ()
#16 0x172d7c in x_delete_frame ()
#17 0xf3524 in delete_frame_internal ()
#18 0x78768 in delete_device_internal ()
#19 0x7035c in delete_console_internal ()
#20 0x87bc4 in Fkill_emacs ()
#21 0x8de24 in funcall_recording_as ()
#22 0x8e170 in Ffuncall ()
#23 0x64580 in $0000004D ()
Cannot access memory at address 0x0.
(gdb)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
$LANG
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
hellcat, (10:45)> echo $LANG
ja_JP.SJIS
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Stack trace from 20.4
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#0 0xc0137598 in kill () from /usr/lib/libc.1
#1 0x64d3c in fatal_error_signal ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#2 <signal handler called>
#3 0xc177d850 in _XimOnKeysCheck () from /usr/lib/X11R6/libX11.2
#4 0xc177da40 in _XimProtoKeypressFilter () from /usr/lib/X11R6/libX11.2
#5 0xc177db24 in _XimFilterKeypress () from /usr/lib/X11R6/libX11.2
#6 0xc174db58 in XFilterEvent () from /usr/lib/X11R6/libX11.2
#7 0xc12e48b4 in DispatchEvent () from /usr/dt/lib/libXt.1
#8 0xc12e553c in DecideToDispatch () from /usr/dt/lib/libXt.1
#9 0xc12e5624 in XtDispatchEvent () from /usr/dt/lib/libXt.1
#10 0xc147c5c4 in RemoveAllPMgr () from /usr/dt/lib/libXm.1
#11 0xc12d90fc in XtCallCallbackList () from /usr/dt/lib/libXt.1
#12 0xc12e0dd0 in Phase2Callbacks () from /usr/dt/lib/libXt.1
#13 0xc12e0d3c in Recursive () from /usr/dt/lib/libXt.1
#14 0xc12e113c in XtPhase2Destroy () from /usr/dt/lib/libXt.1
#15 0xc12e1300 in _XtDoPhase2Destroy () from /usr/dt/lib/libXt.1
#16 0xc12e1484 in XtDestroyWidget () from /usr/dt/lib/libXt.1
#17 0x158a80 in x_delete_frame ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#18 0xd7a20 in delete_frame_internal ()
#19 0xd7b30 in Fdelete_frame ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#20 0x6cd14 in funcall_recording_as ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#21 0x6d358 in Ffuncall ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#22 0x3fb20 in Fbyte_code ()
from
/tmp_mnt/home/dsm/ses/softbench/Code/Softxemacs/Xemacs/xemacs-20.4/src/./xem
acs
#23 <function called from gdb>
1:43 a.m.
Hi David,
>>>> "David" == David S Miller
<dsm(a)fc.hp.com> writes:
core dump in XtDestroyWidget() on HPUX 10.20
I have seen XEmacs core dump while taking dialog boxes down. Specifically,
when a dialog box is completed with a manual entry and a carraige return,
such as File => Save As... type the name and press enter. This does not
seem to happen when mouse selecting OK. It doesn't always happen on the
first try, but I can reliably reproduce this by the third or fourt try.
I'll try to include all relaveent information.
I have reproduced this error on the following versions 20.4,
21.0.67,
and 21.1.2. The included data is from 21.1.2. Version 20.2 DOES NOT
express the error.
What else should be included to make this report complete?
dsm(a)fc.hp.com
Xemacs version 21.1.2 expresses a core dump under the following
conditions:
HPUX 10.20 in Japanese SJIS mode
$LANG=ja_JP.SJIS
HP's X11R6 and Motif1.2_R6 cannot handle Japanese-related functions
correctly, but X11R5 and Motif1.2 can.
For example, ATOK, one of the famous commercial XIM, doesn't work at
all.
Personally, I don't rely on HP's cc (acc) only when I compile GNU
softwares and XEmacs, because sometimes I experienced that HP
compiler's optimizer makes serious bugs when compiling GNU softwares.
Therefore I always use gcc to build XEmacs.
This is my experience.
--
- Hironori Komaba
- mailto:komaba＠jpn.hp.com
1:05 p.m.
Hironori Komaba writes:
: Personally, I don't rely on HP's cc (acc) only when I compile GNU
: softwares and XEmacs, because sometimes I experienced that HP
: compiler's optimizer makes serious bugs when compiling GNU
: softwares. Therefore I always use gcc to build XEmacs.
I don't agree at all. I *never* use gcc on HPUX, mainly because I find
the HP ANSI C compiler to produce far smaller and faster code while
being just as reliable (this is HP92453-01 A.10.32.13 HP C Compiler
versus gcc-2.7.2.1 - I keep intending to build myself an egcs).
To build XEmacs, I use:
export CC="cc"
export CFLAGS="+DAportable +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim
+Olibcalls"
./configure \
--site-includes="/opt/audio/include -I/usr/local/include" \
--site-libraries="/opt/audio/lib -L/usr/local/lib" \
--package-path=/local/packages
I don't use MULE, though.
Cheers,
--
pete
"..."
12:23 p.m.
>>>> "Peter" == Peter Windle
<peterw(a)ugsolutions.com> writes:
I don't agree at all. I *never* use gcc on HPUX, mainly because I
find
the HP ANSI C compiler to produce far smaller and faster code while
being just as reliable (this is HP92453-01 A.10.32.13 HP C Compiler
versus gcc-2.7.2.1 - I keep intending to build myself an egcs).
I don't use MULE, though.
All the problems I mentioned are MULE-related.
For example, XEmacs compiled by HP's cc doesn't handle regular
expressions including Japanese text and some parentheses but XEmacs
compiled by gcc does. This is one of the worst problems for me and
for most Japanese.
I don't know the reason precisely, but I suspect HP's cc. Because its
functionality is extended to be able to handle Japanese text when LANG
is set to ja_JP.SJIS or ja_JP.eucJP, this cause the problems of XEmacs
and so on. HP's cc and C codes related to REGEXP don't seem to be cut
out for each other, maybe.
Therefore I don't use HP's cc ONLY when I compile XEmacs and GNU
softwares.
As far as you use XEmacs in not-Japanese environment with no MULE,
XEmacs compiled by HP's cc (acc) is reliable.
--
- Hironori Komaba
- mailto:komaba＠jpn.hp.com
9309
days inactive
9313
days old
3 comments
3 participants
participants (3)
-
David S. Miller -
Hironori Komaba -
Peter Windle