all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: John Wiegley <jwiegley@gmail.com>,
	22002@debbugs.gnu.org, ander324@purdue.edu
Subject: bug#22002: 24.3; segmentation fault
Date: Fri, 21 Apr 2017 00:31:04 -0400	[thread overview]
Message-ID: <87a87aqt4n.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83vb8jl35p.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Nov 2015 21:04:34 +0200")

tags 22002 unreproducible moreinfo
close 22002
quit

Eli Zaretskii <eliz@gnu.org> writes:

>> From: John Wiegley <jwiegley@gmail.com>
>> Date: Mon, 30 Nov 2015 09:55:43 -0800
>> Cc: 22002@debbugs.gnu.org
>> 
>> >>>>> Peter Anderson <ander324@purdue.edu> writes:
>> 
>> > I went to go run emacs via "emacs introgaugetheory.tex" and received the
>> > following error.
>> 
>> > Fatal error 11: Segmentation fault
>> > Backtrace:
>> > /usr/bin/emacs[0x4f88ab]
>> > /usr/bin/emacs[0x4de47e]
>> > /usr/bin/emacs[0x4f74ae]
>> > /usr/bin/emacs[0x4f7613]
>> 
>> Would it be possible to rebuild your Emacs with debugging enabled, so that we
>> can see the exact location of the error? It looks like your executable has
>> been stripped
>
> Not necessarily.  The node "Crashing" in the Emacs manual describes a
> procedure that can produce file names and line numbers from such
> backtraces.

Since the OP has not responded with output from that procedure, a debug
build, or at all; I'm closing this bug.





      parent reply	other threads:[~2017-04-21  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24  0:36 bug#22002: 24.3; segmentation fault Peter Anderson
2015-11-30 17:55 ` John Wiegley
2015-11-30 19:04   ` Eli Zaretskii
2015-11-30 19:12     ` John Wiegley
2017-04-21  4:31     ` npostavs [this message]

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=87a87aqt4n.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=22002@debbugs.gnu.org \
    --cc=ander324@purdue.edu \
    --cc=eliz@gnu.org \
    --cc=jwiegley@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 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.