emacs-devel
[Top][All Lists]
Advanced

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

Re: Building Emacs from a new MinGW environment


From: Eli Zaretskii
Subject: Re: Building Emacs from a new MinGW environment
Date: Wed, 18 Sep 2013 17:45:47 +0300

> From: Andy Moreton <address@hidden>
> Date: Wed, 18 Sep 2013 14:21:14 +0100
> 
> > Are you building from the source tree, i.e. in-place?  That's what I
> > do, and I just bootstrapped today (twice) with no problems.
> 
> Bzr branch in   c:\emacs\src\emacs\trunk
> Build output in c:\emacs\src\emacs\trunk\build-msys

Can you try building in trunk itself?  I'd like to know if this is in
any way related to the fact that the source and the build trees are
different.

> #6  0x010011ea in address@hidden ()
> No symbol table info available.
> #7  0x75d2fffb in KERNEL32!GetQueuedCompletionStatus () from 
> C:\Windows\syswow64\kernel32.dll
> No symbol table info available.
> #8  0x0088bffc in ?? ()
> No symbol table info available.
> #9  0x76f474ff in ntdll!AlpcMaxAllowedMessageLength () from 
> C:\Windows\SysWOW64\ntdll.dll
> No symbol table info available.
> #10 0x0088bffc in ?? ()
> No symbol table info available.
> #11 0x76f09f45 in ntdll!RtlpNtSetValueKey () from 
> C:\Windows\SysWOW64\ntdll.dll
> No symbol table info available.
> #12 0x01160b7e in sprintf (__stream=0x0, __format=0x1419ae0 "Copying raw data 
> for %.8s...", __format=0x1419ae0 "Copying raw data for %.8s...") at 
> c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../include/stdio.h:269

__stream being NULL in the call to sprintf is the problem, I think.
But the only instances of "Copying raw data for %.8s..." I could find
are in src/unexw32.c and nt/addsection.c, and there the first argument
is a local array that cannot possibly be NULL, so I'm unsure how this
could happen.  Moreover, both unexw32.c and addsection.c are unrelated
to byte-compiling, which just adds to the mystery...

Do you see the same crash if you byte-compile db-ebrowse.el by hand?
If so, try running the same command under GDB, you might get a better
backtrace.  Using the latest port of GDB (7.6.1 should be available)
might also help.



reply via email to

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