unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: VanL <van@scratch.space>
Cc: 36280@debbugs.gnu.org
Subject: bug#36280: 26.2.90; 'emacs -Q' receives SIGSEGV, Segmentation fault
Date: Tue, 18 Jun 2019 19:19:55 +0300	[thread overview]
Message-ID: <83y31ysw5w.fsf@gnu.org> (raw)
In-Reply-To: <m21rzrdll6.fsf@scratch.space> (message from VanL on Wed, 19 Jun 2019 00:17:25 +1000)

> From: VanL <van@scratch.space>
> Date: Wed, 19 Jun 2019 00:17:25 +1000
> 
> The cut-out sections are included as follows:
> 
> 1. 26.2.90 'emacs -Q' runs but has a SIGSEGV before ever being useable
>    a. unfortunately I didn't have symbols included in the build
>    b. see gdb bt
>    c. gmake build completed successfully
>    
> 2. 26.2.90 attempt to 'configure' with symbols and warnings, etc
>    a. gmake build failed to complete

Thanks for your effort.  I guess someone with access top a Darwin
system will have to debug this, because the information you posted
doesn't help in understanding what went wrong.

What is needed is at least a C-level backtrace pointing to the
location in the sources where Emacs crashes.





  reply	other threads:[~2019-06-18 16:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 14:17 bug#36280: 26.2.90; 'emacs -Q' receives SIGSEGV, Segmentation fault VanL
2019-06-18 16:19 ` Eli Zaretskii [this message]
2019-06-18 17:58   ` Robert Pluim
2019-06-18 18:07     ` Eli Zaretskii
2019-06-18 23:20       ` Van L
2019-06-19  7:24         ` Robert Pluim
2019-06-19  7:58           ` VanL
2019-06-19 13:28             ` VanL
2019-06-19 13:38               ` Robert Pluim
2019-06-19 14:02                 ` VanL
2019-06-19 14:32                   ` Robert Pluim
2019-06-20  9:28                     ` VanL
2019-06-20 11:06                       ` Robert Pluim
2019-06-20 13:07                         ` VanL
2019-06-20 13:25                           ` Eli Zaretskii
2019-06-21  3:21                             ` VanL
2019-06-21  5:58                               ` Eli Zaretskii
2019-06-21 11:01                                 ` VanL
2019-06-20 14:25                           ` Robert Pluim
2019-06-22 20:35       ` Alan Third
2022-04-22 13:05 ` Lars Ingebrigtsen
2022-05-22 11:28   ` Lars Ingebrigtsen

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=83y31ysw5w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36280@debbugs.gnu.org \
    --cc=van@scratch.space \
    /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).