all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: John Mastro <john.b.mastro@gmail.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 29183@debbugs.gnu.org
Subject: bug#29183: 27.0.50; SIGSEGV on C-g on Windows
Date: Wed, 08 Nov 2017 20:53:53 +0200	[thread overview]
Message-ID: <83wp30r48u.fsf@gnu.org> (raw)
In-Reply-To: <CAOj2CQRR+pKJanCc32K0uR1R+wH00tfDH-HeWqDh7hm9h8G+qA@mail.gmail.com> (message from John Mastro on Wed, 8 Nov 2017 10:35:06 -0800)

> From: John Mastro <john.b.mastro@gmail.com>
> Date: Wed, 8 Nov 2017 10:35:06 -0800
> Cc: 29183@debbugs.gnu.org
> 
> Ah, thanks. After preprocessing, that line becomes:
> 
> static struct thread_state __attribute__ ((aligned (8))) main_thread;

That's what it should have become...

> >> $ 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.

Hmm... so it sounds like our assumption that this attribute should be
a no-op in this case is incorrect, or maybe it's a bug in GCC 7.2?
Paul?





  reply	other threads:[~2017-11-08 18:53 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
2017-11-08 18:53             ` Eli Zaretskii [this message]
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=83wp30r48u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29183@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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.