all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Masaru Nomiya <nomiya@galaxy.dti.ne.jp>
Cc: emacs-devel@gnu.org
Subject: Re: The very latest emacs (25.1.50) segfault
Date: Sun, 10 Jan 2016 17:56:39 +0200	[thread overview]
Message-ID: <83a8odmnrc.fsf@gnu.org> (raw)
In-Reply-To: <87mvsenicq.wl%nomiya@galaxy.dti.ne.jp> (message from Masaru Nomiya on Sun, 10 Jan 2016 13:55:49 +0900)

> Date: Sun, 10 Jan 2016 13:55:49 +0900
> From: Masaru Nomiya <nomiya@galaxy.dti.ne.jp>
> 
> masaru@linux-uw5l:/tmp/tes/emacs> src/emacs
> Fatal error 11: Segmentation fault
> Backtrace:
> src/emacs[0x4fb622]
> src/emacs[0x4e3384]
> src/emacs[0x4fa52e]
> src/emacs[0x4fa733]
> src/emacs[0x4fa76a]
> /lib64/libpthread.so.0(+0xf1f0)[0x7f8fb6d871f0]
> src/emacs[0x5aeda9]
> src/emacs[0x5b0aea]

Can you use the procedure described in the node "Crashing" of the
Emacs User manual to produce human-readable backtrace with file names
and line numbers out of this?  Otherwise it's impossible for us to
interpret this data.

Thanks.



  reply	other threads:[~2016-01-10 15:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10  4:55 The very latest emacs (25.1.50) segfault Masaru Nomiya
2016-01-10 15:56 ` Eli Zaretskii [this message]
2016-01-11  1:24   ` Masaru Nomiya
2016-01-11  3:39     ` Eli Zaretskii
2016-01-11  4:57       ` Masaru Nomiya
2016-01-11  5:23         ` Masaru Nomiya
2016-01-11 18:25         ` Eli Zaretskii
2016-01-12  9:21           ` 野宮 賢 / NOMIYA Masaru
2016-01-12 20:24           ` K. Handa
     [not found] <87d1t6l389.wl%nomiya@galaxy.dti.ne.jp>
2016-01-14  0:21 ` K. Handa
2016-01-14  1:53   ` Masaru Nomiya
2016-01-14 13:02     ` K. Handa
2016-01-15  4:54       ` Masaru Nomiya
2016-01-20 15:04         ` K. Handa
2016-01-20 23:45           ` Masaru Nomiya
2016-01-21 23:55             ` Masaru Nomiya
2016-01-22 12:48               ` K. Handa
2016-01-14  8:09   ` Masaru Nomiya

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=83a8odmnrc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nomiya@galaxy.dti.ne.jp \
    /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.