From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#35204: 27.0.50; Crash on Cygwin Date: Wed, 10 Apr 2019 17:37:58 +0300 Message-ID: <8336mq6i49.fsf@gnu.org> References: <83ftqr7bnb.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="124689"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 35204@debbugs.gnu.org To: Katsumi Yamaoka Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Apr 10 16:39:12 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hEENc-000WJc-C6 for geb-bug-gnu-emacs@m.gmane.org; Wed, 10 Apr 2019 16:39:12 +0200 Original-Received: from localhost ([127.0.0.1]:60760 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hEENb-0007Q0-ES for geb-bug-gnu-emacs@m.gmane.org; Wed, 10 Apr 2019 10:39:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47326) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hEENT-0007Pb-MO for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2019 10:39:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hEENS-0005oV-Hv for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2019 10:39:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39869) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hEENS-0005nl-9u for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2019 10:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hEENR-00089J-TB for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2019 10:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 10 Apr 2019 14:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 35204 X-GNU-PR-Package: emacs Original-Received: via spool by 35204-submit@debbugs.gnu.org id=B35204.155490709131271 (code B ref 35204); Wed, 10 Apr 2019 14:39:01 +0000 Original-Received: (at 35204) by debbugs.gnu.org; 10 Apr 2019 14:38:11 +0000 Original-Received: from localhost ([127.0.0.1]:53413 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hEEMc-00088I-S7 for submit@debbugs.gnu.org; Wed, 10 Apr 2019 10:38:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:60960) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hEEMY-000884-Vw for 35204@debbugs.gnu.org; Wed, 10 Apr 2019 10:38:07 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35236) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hEEMR-0004zM-Q5; Wed, 10 Apr 2019 10:38:00 -0400 Original-Received: from [176.228.60.248] (port=2463 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hEEMR-0003ir-4W; Wed, 10 Apr 2019 10:37:59 -0400 In-reply-to: (message from Katsumi Yamaoka on Wed, 10 Apr 2019 13:54:16 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.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" Xref: news.gmane.org gmane.emacs.bugs:157462 Archived-At: > Date: Wed, 10 Apr 2019 13:54:16 +0900 > From: Katsumi Yamaoka > Cc: 35204@debbugs.gnu.org > > > Is this when you run Emacs from GDB to begin with? If not, please run > > Emacs from GDB, then the backtrace should be more informative. > > I did so. I rebuilt separately Emacs from scratch from today's > Git repo with no modification on the source using these configure > options > > configure --verbose --with-x-toolkit=gtk3 > > (I detached "CFLAGS=-O0") Does it mean you used "CFLAGS=-O0", or does it mean you did NOT use it? It is better to use it, together with -g3, as that makes debugging easier. > run it from gdb, and I got the backtrace that is in the bottom of > the attached GDB log. It might be too short to analyze, though. Yes, it's still not informative enough. > > How many threads are in the process? Did you type "bt" when the Lisp > > thread was the current one? > > There are 121 threads (IIUC). Is it normal to have so many threads? What are they doing? > I don't konw what is the Lisp thread, sorry. That's usually the thread you get when you type "thread 1" at GDB prompt. But let's see what all those threads do, so please type this: (gdb) thread apply all bt and post the results here. > Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=11, > backtrace_limit=40) at emacs.c:370 > 370 { > (gdb) bt > #0 terminate_due_to_signal (sig=11, backtrace_limit=40) at emacs.c:370 > #1 0x00000001004f134e in handle_fatal_signal (sig=sig@entry=11) > at sysdep.c:1793 > #2 0x00000001004f153f in deliver_thread_signal (sig=sig@entry=11, > handler=0x1004f1340 ) at sysdep.c:1767 > #3 0x00000001004f159f in deliver_fatal_thread_signal (sig=11) at sysdep.c:1805 > #4 handle_sigsegv (sig=11, siginfo=0x1009dea10 , > arg=) at sysdep.c:1890 > #5 0x000000018005f65a in altstack_wrapper (sig=, > siginfo=, sigctx=0xffffde50, > handler=0x1004f1580 ) > at /usr/src/debug/cygwin-3.0.6-1/winsup/cygwin/exceptions.cc:1595 > #6 0x0000000180062dfa in _cygtls::call_signal_handler (this=0xffffce00) > at /usr/src/debug/cygwin-3.0.6-1/winsup/cygwin/exceptions.cc:1777 > #7 0x0000000000000000 in ?? () > Backtrace stopped: previous frame inner to this frame (corrupt stack?) I don't think this is the thread we are interested in. Let's see what "thread apply all bt" shows us. > Lisp Backtrace: > "x-show-tip" (0xffffac20) > "tooltip-show" (0xffffaf60) > "tooltip-help-tips" (0xffffb2c8) > "run-hook-with-args-until-success" (0xffffb2c0) > "tooltip-timeout" (0xffffb670) > "apply" (0xffffb668) > "timer-event-handler" (0xffffb9a8) > (gdb) This seems to be related to showing a tooltip. Do the crashes generally happen when Emacs is supposed to display a tooltip? Also, you say that the 3 commits you identified cause the problem, but those commits are related to the function x-display-monitor-attributes-list. Is this function being called in your usage pattern? Can you put a breakpoint inside that function and see if it breaks, and how often? Thanks.