all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Emacs 21~22 crash on Fedora 10
@ 2009-01-27  7:25 Katsumi Yamaoka
  2009-01-27 11:32 ` Katsumi Yamaoka
  0 siblings, 1 reply; 2+ messages in thread
From: Katsumi Yamaoka @ 2009-01-27  7:25 UTC (permalink / raw)
  To: help-gnu-emacs

Hi,

(Let me replace the old article <b4mk58hbhh5.fsf@jpl.org> with
 this one, because I forgot to add a backtrace.  Sorry.)

Recently Emacs 21.1~22.3 having been installed in the Fedora 10
Linux box got to crash.  Rebuilding does not help.  I guess some
of the recent updates in Fedora 10 caused it, but I'm ignorant
of those changes, sorry.  Emacs 23.0.60, XEmacs 21.4.22 and 21.5-
b28 are all right so far.  Emacs 22.2 that fedora provides through
yum works, too (it will probably be because it was built with the
configure option ``--with-gtk\'').  Has anyone fixed this problem?
Thanks in advance.

The backtrace I caught with Emacs 22.3 built today is attached.
It was built by performing ``./configure --without-xim; make'':

--8<---------------cut here---------------start------------->8---
Configured for `i686-pc-linux-gnu'.

  Where should the build process find the source code?    /Work/emacs-22.3
  What operating system and machine description files should Emacs use?
        `s/gnu-linux.h' and `m/intel386.h'
  What compiler should emacs be built with?               gcc -g -O2 -Wno-pointer-sign
  Should Emacs use the GNU version of malloc?             yes
      (Using Doug Lea's new malloc from the GNU C Library.)
  Should Emacs use a relocating allocator for buffers?    yes
  Should Emacs use mmap(2) for buffer allocation?         no
  What window system should Emacs use?                    x11
  What toolkit should Emacs use?                          LUCID
  Where do we find X Windows header files?                Standard dirs
  Where do we find X Windows libraries?                   Standard dirs
  Does Emacs use -lXaw3d?                                 yes
  Does Emacs use -lXpm?                                   yes
  Does Emacs use -ljpeg?                                  yes
  Does Emacs use -ltiff?                                  yes
  Does Emacs use -lungif?                                 yes
  Does Emacs use -lpng?                                   yes
  Does Emacs use X toolkit scroll bars?                   yes
--8<---------------cut here---------------end--------------->8---

--8<---------------cut here---------------start------------->8---
GNU gdb Fedora (6.8-29.fc10)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
DISPLAY = :0.0
TERM = xterm
Breakpoint 1 at 0x80f2e66: file emacs.c, line 432.
Breakpoint 2 at 0x810d427: file sysdep.c, line 1386.
(gdb) r
Starting program: /tmp/.yamaoka/E23o/emacs-22.3/src/emacs -geometry 80x40+0+0
warning: "/usr/lib/debug/usr/lib/libungif.so.4.1.3.debug": The separate debug info file has no debug info
[Thread debugging using libthread_db enabled]
[New Thread 0x400297e0 (LWP 32283)]
Breakpoint 3 at 0x80ca6f6: file xterm.c, line 7868.

Program received signal SIGSEGV, Segmentation fault.
0x0085d1eb in call_init () at dl-init.c:70
70	      init (argc, argv, env);
(gdb) bt
#0  0x0085d1eb in call_init () at dl-init.c:70
#1  _dl_init (main_map=0x858a2e8, argc=3, argv=0xbffff3c4, env=0xbffff3d4)
    at dl-init.c:134
#2  0x008618d2 in dl_open_worker (a=0xbfffea7c) at dl-open.c:516
#3  0x0085cdb6 in _dl_catch_error (objname=0xbfffeaa4, errstring=0xbfffeaa0, 
    mallocedp=0xbfffeaab, operate=0x861510 <dl_open_worker>, args=0xbfffea7c)
    at dl-error.c:178
#4  0x00860f5e in _dl_open (file=0xbfffec10 "libnss_files.so.2", 
    mode=-2147483647, caller_dlopen=0x0, nsid=-2, argc=3, argv=0xbffff3c4, 
    env=0xbffff3d4) at dl-open.c:596
#5  0x00992492 in do_dlopen (ptr=0xbfffebd4) at dl-libc.c:86
#6  0x0085cdb6 in _dl_catch_error (objname=0xbfffebe4, errstring=0xbfffebe0, 
    mallocedp=0xbfffebeb, operate=0x992430 <do_dlopen>, args=0xbfffebd4)
    at dl-error.c:178
#7  0x00992655 in dlerror_run () at dl-libc.c:47
#8  __libc_dlopen_mode (name=0xbfffec10 "libnss_files.so.2", mode=-2147483647)
    at dl-libc.c:160
#9  0x00969dba in __nss_lookup_function (ni=0x84e6c30, 
    fct_name=0x9b418b "gethostbyname_r") at nsswitch.c:361
#10 0x00969e1f in __nss_lookup (ni=0xbfffecd4, 
    fct_name=0x9b418b "gethostbyname_r", fct2_name=0x0, fctp=0xbfffecd0)
    at nsswitch.c:151
#11 0x0096bd7d in __nss_hosts_lookup2 (ni=0xbfffecd4, 
    fct_name=0x9b418b "gethostbyname_r", fct2_name=0x0, fctp=0xbfffecd0)
    at XXX-lookup.c:76
#12 0x00970e1e in __gethostbyname_r (name=0xbfffed40 "pastis", 
    resbuf=0x9e4ac4, buffer=0x8589ee0 "", buflen=1024, result=0xbfffed18, 
    h_errnop=0xbfffed14) at ../nss/getXXbyYY_r.c:200
#13 0x009705b6 in gethostbyname (name=0xbfffed40 "pastis")
    at ../nss/getXXbyYY.c:116
#14 0x0810cef5 in init_system_name () at sysdep.c:2416
#15 0x0815b14e in init_editfns () at editfns.c:142
#16 0x080f3c3d in main (argc=3, argv=0xbffff3c4) at emacs.c:1683
(gdb) q
The program is running.  Exit anyway? (y or n) 
--8<---------------cut here---------------end--------------->8---

Regards,


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Emacs 21~22 crash on Fedora 10
  2009-01-27  7:25 Emacs 21~22 crash on Fedora 10 Katsumi Yamaoka
@ 2009-01-27 11:32 ` Katsumi Yamaoka
  0 siblings, 0 replies; 2+ messages in thread
From: Katsumi Yamaoka @ 2009-01-27 11:32 UTC (permalink / raw)
  To: help-gnu-emacs

>>>>> Katsumi Yamaoka wrote:
> Recently Emacs 21.1~22.3 having been installed in the Fedora 10
> Linux box got to crash.  Rebuilding does not help.  I guess some
> of the recent updates in Fedora 10 caused it, but I'm ignorant
> of those changes, sorry.
[...]
> The backtrace I caught with Emacs 22.3 built today is attached.
[...]
> Program received signal SIGSEGV, Segmentation fault.
> 0x0085d1eb in call_init () at dl-init.c:70
> 70	      init (argc, argv, env);
> (gdb) bt
> #0  0x0085d1eb in call_init () at dl-init.c:70
> #1  _dl_init (main_map=0x858a2e8, argc=3, argv=0xbffff3c4, env=0xbffff3d4)
>     at dl-init.c:134
> #2  0x008618d2 in dl_open_worker (a=0xbfffea7c) at dl-open.c:516
> #3  0x0085cdb6 in _dl_catch_error (objname=0xbfffeaa4, errstring=0xbfffeaa0,
>     mallocedp=0xbfffeaab, operate=0x861510 <dl_open_worker>, args=0xbfffea7c)
>     at dl-error.c:178
> #4  0x00860f5e in _dl_open (file=0xbfffec10 "libnss_files.so.2",
>     mode=-2147483647, caller_dlopen=0x0, nsid=-2, argc=3, argv=0xbffff3c4,
>     env=0xbffff3d4) at dl-open.c:596
[...]
> #14 0x0810cef5 in init_system_name () at sysdep.c:2416
> #15 0x0815b14e in init_editfns () at editfns.c:142
> #16 0x080f3c3d in main (argc=3, argv=0xbffff3c4) at emacs.c:1683

This seems to be caused by a bug of libnss_files-2.9.so bundled
with glibc-2.9-3.i686.rpm.  Replacing it with libnss_files-2.8.so
of Fedora 9 did the trick.  Now all Emacs 21.1~22.3 revived.
I'll go to the fedora community...


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-01-27 11:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-27  7:25 Emacs 21~22 crash on Fedora 10 Katsumi Yamaoka
2009-01-27 11:32 ` Katsumi Yamaoka

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.