[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Current trunk aborts with MinGW

From: Eli Zaretskii
Subject: Re: Current trunk aborts with MinGW
Date: Tue, 30 Sep 2014 17:44:51 +0300

> Date: Tue, 30 Sep 2014 15:51:55 +0200
> From: martin rudalics <address@hidden>
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]