all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs-26 threads problem [win64]
Date: Tue, 10 Oct 2017 20:55:20 +0200	[thread overview]
Message-ID: <CAFgFV9OEYhKo6G7ZOHDnkEDW3iYYTCASytQU0qafBFKGyagLgQ@mail.gmail.com> (raw)
In-Reply-To: <83vajnotik.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

2017-10-10 18:30 GMT+02:00 Eli Zaretskii <eliz@gnu.org>:

> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Tue, 10 Oct 2017 18:13:19 +0200
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > (gdb) p stack_pos
> > $3 = {__max_align_ll = 0, __max_align_ld = 3.
> 587554638101247699761989924457637e-4943}
>
> What is &stack_pos, the address of stack_pos?  Is it properly aligned?
>
>
(gdb) p &stack_pos
$1 = (max_align_t *) 0xbc1fec0
(gdb) p (char *)&stack_pos
$2 = 0xbc1fec0 ""

I don't see anything wrong here ?

Also, can you tell what Windows exception was translated into SIGSEGV?
> I think GDB will show that information if you issue the following
> command before running the segfaulting program:
>
>   (gdb) set debugexceptions 1
>

[New Thread 1144.0x5860]
gdb: Target exception EXCEPTION_ACCESS_VIOLATION at 0x4001ecb07

Fabrice

[-- Attachment #2: Type: text/html, Size: 1680 bytes --]

      parent reply	other threads:[~2017-10-10 18:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 19:48 Emacs-26 threads problem [win64] Fabrice Popineau
2017-10-10  6:25 ` Eli Zaretskii
2017-10-10 16:13   ` Fabrice Popineau
2017-10-10 16:30     ` Eli Zaretskii
2017-10-10 16:48       ` Eli Zaretskii
2017-10-10 18:57         ` Fabrice Popineau
2017-10-10 19:39           ` Eli Zaretskii
2017-10-10 19:58             ` Fabrice Popineau
2017-10-10 20:09               ` Eli Zaretskii
2017-10-10 20:14                 ` Fabrice Popineau
2017-10-11 10:02                   ` Eli Zaretskii
2017-10-13 18:52                   ` Eli Zaretskii
2017-10-13 22:00                     ` Richard Copley
2017-10-14  6:39                       ` Eli Zaretskii
2017-10-13 22:28                     ` Paul Eggert
2017-10-14  6:47                       ` Eli Zaretskii
2017-10-14  8:05                         ` Paul Eggert
2017-10-14  8:25                           ` Eli Zaretskii
2017-10-14  9:28                             ` Paul Eggert
2017-10-14  9:30                               ` Andreas Schwab
2017-10-14 10:33                                 ` Eli Zaretskii
2017-10-14 11:31                                   ` Andreas Schwab
2017-10-14 12:18                                     ` Eli Zaretskii
2017-10-14 12:39                                       ` Andreas Schwab
2017-10-14 14:00                                         ` Eli Zaretskii
2017-10-14 22:51                                           ` Paul Eggert
2017-10-15 15:14                                             ` Eli Zaretskii
2017-10-15 15:39                                               ` Andreas Schwab
2017-10-15 16:30                                                 ` Eli Zaretskii
2017-10-15 16:41                                                   ` Stefan Monnier
2017-10-15 17:19                                                     ` Eli Zaretskii
2017-10-15 16:47                                                   ` Andreas Schwab
2017-10-14  9:26                           ` Andreas Schwab
2017-10-14  9:31                             ` Paul Eggert
2017-10-14 19:06                           ` Fabrice Popineau
2017-10-10 18:55       ` Fabrice Popineau [this message]

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=CAFgFV9OEYhKo6G7ZOHDnkEDW3iYYTCASytQU0qafBFKGyagLgQ@mail.gmail.com \
    --to=fabrice.popineau@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.