[Top][All Lists]

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

Re: Emacs 23.1.96 (git HEAD) crashing at startup.

From: Ashish SHUKLA
Subject: Re: Emacs 23.1.96 (git HEAD) crashing at startup.
Date: Sun, 02 May 2010 10:33:09 +0530
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.96 (x86_64-unknown-linux-gnu)

Eli Zaretskii writes:
>> Date: Sun, 2 May 2010 05:34:18 +0530
>> From: Ashish SHUKLA <address@hidden>
>> I recently compiled and install Emacs 23.1.96 from git with following
>> commit at HEAD:
>> commit 95e831252b5e23a0682df8a29081c146ada78b76
>> Author: Eli Zaretskii <address@hidden>
>> Date:   Sat May 1 21:50:20 2010 +0300
>> composite.el (compose-region, reference-point-alist): Fix typos in the doc
>> strings.

> I surely hope fixing typos in doc strings cannot cause any crashes ;-)


>> After installing, I started it using "emacs -Q" it crashes during
>> startup. Following is the output of 'bt full' from gdb:

Sorry, that was supposed to be "emacs -Q -nw" (ncurses version).

> Please start GDB from the src directory, and please post here also the
> results of the xbacktrace command (the Lisp backtrace).

--8<---------------cut here---------------start------------->8---
(gdb) xbacktrace 
"global-font-lock-mode" (0xffffce48)
"custom-set-minor-mode" (0xffffcff8)
"custom-reevaluate-setting" (0xffffd1c8)
"mapc" (0xffffd2f8)
"command-line" (0xffffd4d8)
"normal-top-level" (0xffffd610)
--8<---------------cut here---------------end--------------->8---

When started emacs as with "emacs -Q" (X11 version), it crashed with following
backtrace, but no 'xbacktrace'.

--8<---------------cut here---------------start------------->8---
(gdb) bt
#0  0x0000000000438b63 in display_line (it=0x7fffffffb470) at xdisp.c:16536
#1  0x000000000043d800 in try_window (window=<value optimized out>, pos=..., 
check_margins=0) at xdisp.c:13983
#2  0x000000000043da54 in display_echo_area_1 (a1=<value optimized out>, 
a2=<value optimized out>, a3=<value optimized out>, a4=<value optimized out>) 
at xdisp.c:8615
#3  0x000000000042be26 in with_echo_area_buffer (w=0x1148680, which=<value 
optimized out>, fn=0x43da00 <display_echo_area_1>, a1=18122368, a2=11647378, 
a3=0, a4=0)
    at xdisp.c:8394
#4  0x000000000043f119 in display_echo_area (update_frame_p=0) at xdisp.c:8575
#5  echo_area_display (update_frame_p=0) at xdisp.c:9173
#6  0x000000000043e277 in redisplay_internal (preserve_echo_area=<value 
optimized out>) at xdisp.c:11487
#7  0x000000000043ef83 in redisplay_preserve_echo_area (from_where=<value 
optimized out>) at xdisp.c:12037
#8  0x00000000005989c9 in wait_reading_process_output (time_limit=0, 
microsecs=0, read_kbd=<value optimized out>, do_display=1, 
wait_for_cell=11647378, wait_proc=0x0, 
    just_wait_proc=0) at process.c:4887
#9  0x00000000004ee51e in kbd_buffer_get_event (commandflag=1, nmaps=2, 
maps=0x7fffffffd490, prev_event=11647378, used_mouse_menu=0x7fffffffd59c, 
end_time=0x0) at keyboard.c:4135
#10 read_char (commandflag=1, nmaps=2, maps=0x7fffffffd490, 
prev_event=11647378, used_mouse_menu=0x7fffffffd59c, end_time=0x0) at 
#11 0x00000000004f0493 in read_key_sequence (keybuf=<value optimized out>, 
prompt=11647378, dont_downcase_last=0, can_return_switch_frame=1, 
fix_current_buffer=1, bufsize=30)
    at keyboard.c:9512
#12 0x00000000004f22d1 in command_loop_1 () at keyboard.c:1643
#13 0x000000000055497f in internal_condition_case (bfun=0x4f2100 
<command_loop_1>, handlers=11714642, hfun=0x4e6820 <cmd_error>) at eval.c:1490
#14 0x00000000004e566e in command_loop_2 () at keyboard.c:1360
#15 0x000000000055485a in internal_catch (tag=11707458, func=0x4e5650 
<command_loop_2>, arg=11647378) at eval.c:1226
#16 0x00000000004e6a21 in command_loop () at keyboard.c:1339
#17 0x00000000004e6aba in recursive_edit_1 () at keyboard.c:954
#18 0x00000000004e6bf6 in Frecursive_edit () at keyboard.c:1016
#19 0x00000000004e23d5 in main (argc=<value optimized out>, 
argv=0x7fffffffde68) at emacs.c:1833
--8<---------------cut here---------------end--------------->8---

> Can you cause this crash in an unoptimized build as well?  If so, the
> backtrace from that will be much more helpful.

No crashes with unoptimized build.

--8<---------------cut here---------------start------------->8---
abbe [emacs-git] chateau % ld -v
GNU ld (GNU Binutils)
abbe [emacs-git] chateau % gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --prefix=/usr 
--enable-languages=c,c++,fortran,objc,obj-c++,ada --enable-shared 
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-lto 
--enable-gnu-unique-object --disable-multilib --disable-libstdcxx-pch 
--with-system-zlib --with-ppl --with-cloog --libdir=/usr/lib 
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
Thread model: posix
gcc version 4.5.0 (GCC) 
abbe [emacs-git] chateau % fgrep CFLAGS /etc/makepkg.conf       
CFLAGS="-march=x86-64 -mtune=native -O2 -pipe -g"
--8<---------------cut here---------------end--------------->8---


Sent via Gnus from GNU Emacs

Attachment: pgpTHzIuYC6V2.pgp
Description: PGP signature

reply via email to

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