From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.comp.lib.gnulib.bugs Subject: Re: [master b3cf281] Unbreak the MinGW build Date: Fri, 16 Dec 2016 23:10:59 +0200 Message-ID: <83y3zf7f6k.fsf@gnu.org> References: <83eg1887q4.fsf@gnu.org> <6f53d9d5-c352-2bb7-1312-d7e465b63c61@cs.ucla.edu> <10588713.4sEyyCWImg@linuix.haible.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1481922715 10737 195.159.176.226 (16 Dec 2016 21:11:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 16 Dec 2016 21:11:55 +0000 (UTC) Cc: eggert@cs.ucla.edu, bug-gnulib@gnu.org, emacs-devel@gnu.org To: Bruno Haible Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 16 22:11:51 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cHznB-0001n8-53 for ged-emacs-devel@m.gmane.org; Fri, 16 Dec 2016 22:11:49 +0100 Original-Received: from localhost ([::1]:34310 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHznE-0005va-0K for ged-emacs-devel@m.gmane.org; Fri, 16 Dec 2016 16:11:52 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37005) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHzn8-0005vF-1l for emacs-devel@gnu.org; Fri, 16 Dec 2016 16:11:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cHzn3-00022m-Kz for emacs-devel@gnu.org; Fri, 16 Dec 2016 16:11:45 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60708) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHzn3-00022h-I2; Fri, 16 Dec 2016 16:11:41 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3077 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cHzn2-0006if-Db; Fri, 16 Dec 2016 16:11:41 -0500 In-reply-to: <10588713.4sEyyCWImg@linuix.haible.de> (message from Bruno Haible on Fri, 16 Dec 2016 19:11:31 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:210544 gmane.comp.lib.gnulib.bugs:36537 Archived-At: > From: Bruno Haible > Cc: bug-gnulib@gnu.org, Paul Eggert , emacs-devel@gnu.org > Date: Fri, 16 Dec 2016 19:11:31 +0100 > > On mingw, the fpending.o generated by this code, with or without this > #include , is identical (even with debugging information [-g]). Yes, I said that much. Which is why this is a mystery in my eyes. > I wouldn't have applied this patch, as the cause of the crash is obviously > somewhere else. I know. I just don't know where, and have run out of ideas. Suggestions welcome, but I cannot continue my work on Emacs without being able to build the latest HEAD of the master branch. Having uncommitted/unpushed changes in master means I need to jump through hoops each time I need to push a change upstream. > - How often have you tried to temacs+dump with and without the change? > Once each? Twice each? 10 times each? If it's a small number, you may > be seeing a random result and not realize it was random. I did it in two separate branches, 3 times in each one. The results are consistent. This crash isn't random. > - Did you run temacs in the same directory in both cases, or in different > directories? Different directories could lead to a different memory > layout in temacs, due to different filename lengths. Same directory. > - After determining that disabling the include would fix the crash, did > you test whether reenable the include would reenable the crash? Yes.