[Top][All Lists]

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

bug#14569: 24.3.50; bootstrap fails on Cygwin

From: Ken Brown
Subject: bug#14569: 24.3.50; bootstrap fails on Cygwin
Date: Wed, 19 Jun 2013 23:00:36 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6

On 6/19/2013 10:45 PM, Eli Zaretskii wrote:
Date: Wed, 19 Jun 2013 16:24:02 -0400
From: Ken Brown <address@hidden>
CC: address@hidden, address@hidden,
         Paul Eggert <address@hidden>

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.

No, I think these failures didn't go through 'abort', that's why you
didn't get the backtrace.  You need to look at the pthread sources in
the file mentioned, and find out where to put the breakpoint to catch
that error.

The error message comes from 'g_thread_abort', which calls 'abort'. The reason there was no backtrace is exactly what I said. I know that's the case because I removed the "@" at the beginning of the Makefile rule so that the command would get echoed, but it didn't get echoed in the compilation above (and others like it). On the other hand, it did get echoed in the SIGSEGV examples that I mentioned in my previous mail.


reply via email to

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