From: Eli Zaretskii <eliz@gnu.org>
To: John Mastro <john.b.mastro@gmail.com>
Cc: 29183@debbugs.gnu.org
Subject: bug#29183: 27.0.50; SIGSEGV on C-g on Windows
Date: Wed, 08 Nov 2017 05:43:05 +0200 [thread overview]
Message-ID: <834lq5saeu.fsf@gnu.org> (raw)
In-Reply-To: <CAOj2CQTdK8COt3xSdDBPptWXnFvZN+1a8QPzs+AFXMNQibFuog@mail.gmail.com> (message from John Mastro on Tue, 7 Nov 2017 13:24:15 -0800)
> From: John Mastro <john.b.mastro@gmail.com>
> Date: Tue, 7 Nov 2017 13:24:15 -0800
> Cc: 29183@debbugs.gnu.org
>
> > Can you show a preprocessed version of thread.c, where it does this:
> >
> > static struct thread_state GCALIGNED main_thread;
>
> What's the right invocation to get that?
You need to display it first. Like this:
$ cd src
$ make thread.o -W thread.c V=1
This will compile thread.c and show the full command it uses to do
that. Copy-paste that command at the shell prompt, but this time
replace -c (or add if -c is not there) with -E, and also add
"-o thread.ii" to the command line. Then hit Enter. The file
thread.ii will have the preprocessed source.
> $ gcc --version
> gcc.exe (Rev1, Built by MSYS2 project) 7.2.0
Should be okay, I think. Does the problem go away if you remove
GCALIGNED from that line in thread.c and rebuild?
next prev parent reply other threads:[~2017-11-08 3:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 21:58 bug#29183: 27.0.50; SIGSEGV on C-g on Windows John Mastro
2017-11-07 3:36 ` Eli Zaretskii
2017-11-07 18:14 ` John Mastro
2017-11-07 19:41 ` Eli Zaretskii
2017-11-07 21:24 ` John Mastro
2017-11-08 3:43 ` Eli Zaretskii [this message]
2017-11-08 18:35 ` John Mastro
2017-11-08 18:53 ` Eli Zaretskii
2017-11-08 22:46 ` Paul Eggert
2017-11-08 23:41 ` John Mastro
2017-11-09 4:56 ` Paul Eggert
2017-11-09 17:59 ` John Mastro
2017-11-09 14:59 ` Davor Rotim
2017-11-09 17:04 ` Eli Zaretskii
2017-11-09 18:10 ` Davor Rotim
2017-12-01 10:00 ` Noam Postavsky
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=834lq5saeu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29183@debbugs.gnu.org \
--cc=john.b.mastro@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.