From: Robert Pluim <rpluim@gmail.com>
To: VanL <van@scratch.space>
Cc: 36280@debbugs.gnu.org
Subject: bug#36280: 26.2.90; 'emacs -Q' receives SIGSEGV, Segmentation fault
Date: Thu, 20 Jun 2019 13:06:49 +0200 [thread overview]
Message-ID: <m25zp0ldme.fsf@gmail.com> (raw)
In-Reply-To: <AE0FD373-4512-4CC1-920E-8CB644438F9A@scratch.space> (VanL's message of "Thu, 20 Jun 2019 19:28:35 +1000")
>>>>> On Thu, 20 Jun 2019 19:28:35 +1000, VanL <van@scratch.space> said:
>> On 20 Jun 2019, at 00:32, Robert Pluim <rpluim@gmail.com> wrote:
>>
>> Strange. Iʼve just built from the tarball both in-tree and out-of tree
>> without any issues (but Iʼm not targeting X11/GTK), so I donʼt
>> understand why building from git makes any difference for you.
VanL> Maybe, your macOS has the 'macuvs.h' in the environment for the out-of tree case.
Itʼs part of the emacs source code, so thatʼs highly unlikely.
VanL> -----
VanL> I was able to build and run using 'clang' for X11/GTK2 and got the 'Segmentation fault'.
VanL> Previously, for X11/GTK2 I was able to build and run successfully for 26.1, 26.1.90, 26.2, 27.
VanL> Something about 26.2.90 is a show stopper for X11/GTK2.
VanL> I don't know the options to give 'clang' to help 'gdb' with symbols and such.
either call configure with CFLAGS="-O0 -g3", or do
make CFLAGS="-O0 -g3"
after the configure step.
Robert
next prev parent reply other threads:[~2019-06-20 11:06 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
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 [this message]
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=m25zp0ldme.fsf@gmail.com \
--to=rpluim@gmail.com \
--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).