GNU bug report logs -
#14569
24.3.50; bootstrap fails on Cygwin
Previous Next
Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>
Date: Fri, 7 Jun 2013 00:17:01 UTC
Severity: important
Found in version 24.3.50
Done: Ken Brown <kbrown <at> cornell.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On 6/18/2013 11:53 AM, Eli Zaretskii wrote:
> As for displaying the backtrace, just add the "bt" command to the
> chain, like this:
>
> emacsdbg = EMACSLOADPATH=$(lisp) LC_ALL=C gdb --batch --return-child-result -ex 'b abort' -ex run -ex bt -ex cont --args $(EMACS) $(EMACSOPT)
>
> GDB executes the commands given via -ex in order, so think of this as
> if you typed the commands whenever GDB shows its prompt.
Thanks, Eli. I replaced "bt" by "thread apply all bt", which probably
didn't provide additional useful information. I then ran "make
bootstrap" followed by repeated "make -k" until the bootstrap completed.
Early in the process there were two crashes with SIGSEGV, for which I
got backtraces (attached). In both cases the crash occurred in
gmalloc.c, which probably explains why we're seeing problems only on Cygwin.
After that there were many compile failures with errors like those that
others have reported:
Compiling gnus/gnus-cache.el
GLib (gthread-posix.c): Unexpected error from C library during
'pthread_setspecific': Invalid argument. Aborting.
Makefile:254: recipe for target `gnus/gnus-cache.elc' failed
But these compilations didn't invoke gdb, apparently because they
involved Makefile targets other than compile-onefile. So I didn't get
any more backtraces.
I can modify the Makefile further if necessary, but the attached
backtraces are a start.
Ken
[backtrace5.txt (text/plain, attachment)]
[backtrace6.txt (text/plain, attachment)]
This bug report was last modified 11 years and 314 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.