GNU bug report logs - #12703
segfault in 0x0000000100087491 in char_table_ref () at chartab.c:233 (emacs-24.2.50.1, osx-10.8.2)

Previous Next

Packages: ns, emacs;

Reported by: Leif Walsh <leif.walsh <at> gmail.com>

Date: Mon, 22 Oct 2012 15:57:02 UTC

Severity: normal

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Leif Walsh <leif.walsh <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "12703 <at> debbugs.gnu.org" <12703 <at> debbugs.gnu.org>
Subject: bug#12703: segfault in 0x0000000100087491 in char_table_ref () at chartab.c:233 (emacs-24.2.50.1, osx-10.8.2)
Date: Mon, 22 Oct 2012 14:15:50 -0400
Thanks. I won't be able to try this until tomorrow probably (on work computer, went home for the afternoon). 

Sent from my iPhone

On Oct 22, 2012, at 13:03, Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: Leif Walsh <leif.walsh <at> gmail.com>
>> Date: Mon, 22 Oct 2012 11:13:35 -0400
>> 
>> I am getting a pretty reproducible bug in my own build of
>> emacs-24.2.50.1 on osx-10.8.2 with the "lion fullscreen patch" from
>> somewhere.
>> 
>> Build info:
>> 
>> git://git.savannah.gnu.org/emacs.git <at> fbfb2416
>> additional patch attached in fullscreen.patch
>> config.log attached
> 
> Which bzr version is that?  What is the last entry that you see in
> src/ChangeLog?
> 
>> Steps to reproduce:
>> 
>> 1. Install auto-complete-1.3.1 and git://github.com/brianjcj/auto-complete-clang
>> 2. Visit a c++ file
>> 3. Try completing some stuff
>> 4. Segfaults after not too much messing around
>> 
>> Backtrace:
>> 
>> (gdb) bt
>> #0  0x00007fff96242d46 in __kill ()
>> #1  0x000000010009f63e in fatal_error_backtrace (sig=6,
>> backtrace_limit=6) at emacs.c:331
>> #2  0x00000001000bc5b3 in emacs_abort () at sysdep.c:1830
>> #3  0x000000010018c73d in ns_term_shutdown (sig=<value temporarily
>> unavailable, due to optimizations>) at nsterm.m:4229
>> #4  0x000000010009f5f1 in fatal_error_backtrace (sig=11,
>> backtrace_limit=10) at emacs.c:314
>> #5  0x00000001000a1cde in handle_fatal_signal (sig=<value temporarily
>> unavailable, due to optimizations>) at emacs.c:287
>> #6  0x00000001000bc80d in handle_on_main_thread (sig=11,
>> handler=0x1000a1cd0 <handle_fatal_signal>) at sysdep.c:1493
>> #7  <signal handler called>
>> #8  0x0000000100087491 in char_table_ref () at chartab.c:233
>> #9  0x000000010016fadf in composition_compute_stop_pos
>> (cmp_it=0x7fff5fbf2770, charpos=4195335, bytepos=5, endpos=4300718816,
>> string=140734799751024) at composite.c:1053
>> #10 0x000000010002e701 in compute_stop_pos (it=0x7fff5fbf4c40) at xdisp.c:3393
>> #11 0x000000010002fdcb in next_element_from_string (it=0x7fff5fbf43d8)
>> at xdisp.c:7525
> 
> A very similar bug #101159 was fixed a month ago in revision 110135.
> If your Emacs is older than that, you need to update your sources and
> rebuild.




This bug report was last modified 12 years and 206 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.