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: Tue, 7 Nov 2017 13:24:15 -0800 [thread overview]
Message-ID: <CAOj2CQTdK8COt3xSdDBPptWXnFvZN+1a8QPzs+AFXMNQibFuog@mail.gmail.com> (raw)
In-Reply-To: <83d14tswq6.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> wrote:
>> > Is this again bug#29040? Did main_thread become mis-aligned again?
>> I repeated the commands Richard used in that bug report, and I believe
>> you're right: it's 8-byte aligned rather than 16-byte aligned.
>> Transcript below.
> Yep. How did that happen?..
>
> 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? I tried some variations on:
gcc -E -mtune=generic -l/mingw64/include -l/c/home/jbm/src/emacs
-l/c/home/jbm/src/emacs/src -l/c/home/jbm/src/emacs/nt/inc src/thread.c
But always got an error:
src/thread.c:20:10: fatal error: config.h: No such file or directory
> Also, what is your GCC version?
$ gcc --version
gcc.exe (Rev1, Built by MSYS2 project) 7.2.0
Thanks
next prev parent reply other threads:[~2017-11-07 21:24 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 [this message]
2017-11-08 3:43 ` Eli Zaretskii
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
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=CAOj2CQTdK8COt3xSdDBPptWXnFvZN+1a8QPzs+AFXMNQibFuog@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).