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
Hello.
11 jun 2013 kl. 22:06 skrev Ken Brown <kbrown <at> cornell.edu>:
> On 6/11/2013 3:53 PM, Eli Zaretskii wrote:
>>> Date: Tue, 11 Jun 2013 15:26:56 -0400
>>> From: Ken Brown <kbrown <at> cornell.edu>
>>> CC: Eli Zaretskii <eliz <at> gnu.org>, 14569 <at> debbugs.gnu.org,
>>> angelo.graziosi <at> alice.it
>>>
>>> No. This does not happen. The Cygwin glib maintainer takes pains to
>>> patch the source if necessary to make sure that Cygwin is not treated
>>> like Windows. See, for instance, the attached patch that is used in the
>>> Cygwin build.
>>
>> So, in this patched glib, what does g_spawn_close_pid do, and under
>> what circumstances could it call 'abort'?
>
> It does nothing. So Jan's backtrace is suspect. I don't know if that could result from optimization, but I'll build a non-optimized glib and see if I can get a more reliable backtrace.
>
It is suspect, the error message does belong to g_private_set (frame #2). Frame #1 should have been g_thread_abort. If there is indeed a memory corruption, such as a stack overwrite, that might explain it. Or it might just be that gdb is in error.
The build BTW, was un-optimized.
Jan D.
This bug report was last modified 12 years ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.