From: Eli Zaretskii <eliz@gnu.org>
To: Leif Walsh <leif.walsh@gmail.com>
Cc: 12703@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 19:03:27 +0200 [thread overview]
Message-ID: <83objucucg.fsf@gnu.org> (raw)
In-Reply-To: <CAOa4Uz+8gEWT8FzSTCz2ufDUM=s1+_epuuCN1zHu_T+KsTaPog@mail.gmail.com>
> From: Leif Walsh <leif.walsh@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@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.
next prev parent reply other threads:[~2012-10-22 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 15:13 bug#12703: segfault in 0x0000000100087491 in char_table_ref () at chartab.c:233 (emacs-24.2.50.1, osx-10.8.2) Leif Walsh
2012-10-22 17:03 ` Eli Zaretskii [this message]
2012-10-22 18:15 ` Leif Walsh
2012-11-03 19:06 ` Glenn Morris
2012-11-03 19:10 ` Leif Walsh
2012-10-22 21:17 ` Jan Djärv
2012-10-22 21:25 ` Leif Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83objucucg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12703@debbugs.gnu.org \
--cc=leif.walsh@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).