unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Current trunk aborts with MinGW
Date: Tue, 30 Sep 2014 17:44:51 +0300	[thread overview]
Message-ID: <83k34lkw0s.fsf@gnu.org> (raw)
In-Reply-To: <542AB57B.8080000@gmx.at>

> Date: Tue, 30 Sep 2014 15:51:55 +0200
> From: martin rudalics <rudalics@gmx.at>
> 
> The problem is in this part of frame.c
> 
> 	  tem = display_x_get_resource
> 	    (dpyinfo, SCOPED_STRING (attribute),
> 	     SCOPED_STRING (class), Qnil, Qnil);
> 
> but I have no idea how to investigate this.

When one of the functions that create "scoped" Lisp objects aborts,
the first thing to look at is the addresses of the stack variables:
if they are not 8-byte aligned, that's the reason.  For example:

> #1  0x01173d6b in die (msg=0x14bb004 "XTYPE (a) == type && XUNTAG (a, type) == ptr", file=0x14baf34 "lisp.h", line=926) at alloc.c:7111

See the address of 'msg'?  It's clearly aligned on a 4-byte boundary.



  parent reply	other threads:[~2014-09-30 14:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30  8:25 Current trunk aborts with MinGW martin rudalics
2014-09-30 13:01 ` Andy Moreton
2014-09-30 13:51   ` martin rudalics
2014-09-30 14:19     ` Andy Moreton
2014-09-30 15:57       ` martin rudalics
2014-09-30 14:44     ` Eli Zaretskii [this message]
2014-09-30 15:58       ` martin rudalics
2014-09-30 16:07         ` Eli Zaretskii
2014-09-30 16:24           ` martin rudalics
2014-09-30 14:02   ` Eli Zaretskii
2014-09-30 13:59 ` Eli Zaretskii
2014-09-30 14:11   ` martin rudalics
2014-09-30 14:36     ` Eli Zaretskii
2014-09-30 14:33 ` Stefan Monnier
2014-09-30 14:42   ` Eli Zaretskii
2014-09-30 15:57     ` martin rudalics
2014-09-30 17:41       ` Eli Zaretskii

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=83k34lkw0s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).