Re: Current trunk aborts with MinGW

[martin rudalics]

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

I wouldn't even have known that 0x14bb004 denotes a stack address.  And
then look whether it ends with "4" or "C" ...

Thanks, martin