all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 21660@debbugs.gnu.org
Subject: bug#21660: 25.0.50; backtrace
Date: Sun, 11 Oct 2015 05:41:34 +0300	[thread overview]
Message-ID: <83io6eqg81.fsf@gnu.org> (raw)
In-Reply-To: <871td2qvhf.fsf@udel.edu>

> From: Mark Oteiza <mvoteiza@udel.edu>
> Date: Sat, 10 Oct 2015 17:11:56 -0400
> 
> 
> I've had a couple SEGVs starting on 01 Oct. Here's a backtrace--in the
> event it's not useful I'm running unoptimized to hopefully catch it
> again.
> 
> #0  0x00007f8574ee9c39 in raise () from /usr/lib/libpthread.so.0
> No symbol table info available.
> #1  0x00000000004e6634 in terminate_due_to_signal (sig=sig@entry=11, 
>     backtrace_limit=backtrace_limit@entry=40) at emacs.c:397
> No locals.
> #2  0x00000000004fe33e in handle_fatal_signal (sig=sig@entry=11) at sysdep.c:1593
> No locals.
> #3  0x00000000004fe563 in deliver_thread_signal (sig=sig@entry=11, 
>     handler=0x4fe330 <handle_fatal_signal>) at sysdep.c:1567
> No locals.
> #4  0x00000000004fe5cf in deliver_fatal_thread_signal (sig=11) at sysdep.c:1605
> No locals.
> #5  handle_sigsegv (sig=11, siginfo=<optimized out>, arg=<optimized out>)
>     at sysdep.c:1687
>         fatal = <optimized out>
> #6  <signal handler called>
> No symbol table info available.
> #7  turn_on_face (f=0x46d5cc8, face_id=28) at term.c:1902
>         face = 0x0

The cause is again a face that was removed from the face cache.  I
need the same data as requested in bug #21428, and yes, from an
unoptimized build.

Thanks.





  reply	other threads:[~2015-10-11  2:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10 21:11 bug#21660: 25.0.50; backtrace Mark Oteiza
2015-10-11  2:41 ` Eli Zaretskii [this message]
2016-12-07 18:41   ` Glenn Morris
2016-12-07 19:00     ` Mark Oteiza

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83io6eqg81.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21660@debbugs.gnu.org \
    --cc=mvoteiza@udel.edu \
    /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 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.