From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#13546: 24.2.92; Error(s) when sending emails Date: Wed, 13 Feb 2013 19:20:44 +0200 Message-ID: <83pq043zbn.fsf@gnu.org> References: <86ehh9mx93.fsf@somewhere.org> <86libhfj7x.fsf@somewhere.org> <86ham5ffc5.fsf@somewhere.org> <861ud9gsh9.fsf@somewhere.org> <86ip5x3do6.fsf@somewhere.org> <867gmdl73l.fsf@somewhere.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1360776097 2243 80.91.229.3 (13 Feb 2013 17:21:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Feb 2013 17:21:37 +0000 (UTC) Cc: 13546@debbugs.gnu.org To: Sebastien Vauban Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Feb 13 18:21:59 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U5g1u-0005pP-1U for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Feb 2013 18:21:58 +0100 Original-Received: from localhost ([::1]:60665 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5g1a-0001Ni-Jb for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Feb 2013 12:21:38 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:34181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5g1X-0001NN-H7 for bug-gnu-emacs@gnu.org; Wed, 13 Feb 2013 12:21:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5g1S-0005Ss-4n for bug-gnu-emacs@gnu.org; Wed, 13 Feb 2013 12:21:35 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:48962) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5g1S-0005So-1j for bug-gnu-emacs@gnu.org; Wed, 13 Feb 2013 12:21:30 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1U5g1y-00051g-5x for bug-gnu-emacs@gnu.org; Wed, 13 Feb 2013 12:22:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Feb 2013 17:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13546 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13546-submit@debbugs.gnu.org id=B13546.136077610119293 (code B ref 13546); Wed, 13 Feb 2013 17:22:02 +0000 Original-Received: (at 13546) by debbugs.gnu.org; 13 Feb 2013 17:21:41 +0000 Original-Received: from localhost ([127.0.0.1]:54426 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U5g1d-000518-3C for submit@debbugs.gnu.org; Wed, 13 Feb 2013 12:21:41 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:35472) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U5g1a-00050y-NZ for 13546@debbugs.gnu.org; Wed, 13 Feb 2013 12:21:40 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MI6007005G6LS00@a-mtaout22.012.net.il> for 13546@debbugs.gnu.org; Wed, 13 Feb 2013 19:20:29 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MI6005VU5I5PYE1@a-mtaout22.012.net.il>; Wed, 13 Feb 2013 19:20:29 +0200 (IST) In-reply-to: <867gmdl73l.fsf@somewhere.org> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:71188 Archived-At: > From: "Sebastien Vauban" > Cc: 13546@debbugs.gnu.org > Date: Tue, 12 Feb 2013 19:28:30 +0100 > > Breakpoint 2, sys_read (fd=6, buffer=0x64b1034 "", count=5) at w32.c:6410 > 6410 in w32.c > (gdb) > Continuing. > warning: sys_read called when read is in progress > warning: reader_thread.SetEvent failed with 6 for fd 6 > [New Thread 15276.0x6774] > warning: reader_thread.SetEvent failed with 6 for fd 3 > warning: reader_thread.SetEvent failed with 6 for fd 5 > [New Thread 15276.0x5b0c] > [New Thread 15276.0x1898] It's weird, these messages. I cannot figure out what causes them. I see in your screencast that helm launches subprocesses like crazy (it looks like every pattern character you type runs another Locate process). But even if I try simulating such a subprocess pressure, by launching another 'locate' command every 100 msec, I cannot reproduce the above messages on my system. So some other factor is at work here. I need more data. Please modify the way you set breakpoint at w32.c:6410 as follows: (gdb) break w32.c:6410 (gdb) commands > bt 4 > p fd > p fd_info[fd] > b *cp > continue > end In addition, please add a 3rd breakpoint, like this: (gdb) break w32proc.c:2276 (gdb) commands > bt 5 > p cp > p cp->wnd > continue > end Please do this right at the beginning of a fresh session, and please post the entire GDB session until it gets to the "unusable" state. (You may need to enlarge the Screen Buffer Size property of the cmd window in which you run GDB, for it to be able to keep all those message and backtraces.) It is very important for me to see all the messages and backtraces one after the other, to see how the problem develops. Also, do you per chance have w32-start-process-share-console customized to a non-nil value? If so, can you try with it being nil? > (gdb) p *cp > $9 = {fd = 3, pid = -1, char_avail = 0x318, char_consumed = 0x314, thrd = 0x31c, hwnd = 0x0, > procinfo = {hProcess = 0x0, hThread = 0x0, dwProcessId = 0, dwThreadId = 0}, status = 1, > chr = 22 '\026', ovl_read = {Internal = 0, InternalHigh = 0, {{Offset = 0, OffsetHigh = 0}, Not sure if this is important, but every time this breakpoint breaks, the character read from the pipe is \026, i.e. Ctrl-V. Does that ring any bells?