From: John Mastro <john.b.mastro@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29183@debbugs.gnu.org
Subject: bug#29183: 27.0.50; SIGSEGV on C-g on Windows
Date: Wed, 8 Nov 2017 10:35:06 -0800 [thread overview]
Message-ID: <CAOj2CQRR+pKJanCc32K0uR1R+wH00tfDH-HeWqDh7hm9h8G+qA@mail.gmail.com> (raw)
In-Reply-To: <834lq5saeu.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> wrote:
>> > 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.
Ah, thanks. After preprocessing, that line becomes:
static struct thread_state __attribute__ ((aligned (8))) main_thread;
>> $ 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?
Yep, the SIGSEGV is gone if I remove GCALIGNED from that line.
Thanks
John
next prev parent reply other threads:[~2017-11-08 18:35 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
2017-11-08 18:35 ` John Mastro [this message]
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
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=CAOj2CQRR+pKJanCc32K0uR1R+wH00tfDH-HeWqDh7hm9h8G+qA@mail.gmail.com \
--to=john.b.mastro@gmail.com \
--cc=29183@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).