From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44313: 27.1.50; ns_mouse_position EXC_BAD_ACCESS crash Date: Fri, 30 Oct 2020 21:07:46 +0200 Message-ID: <83eelfa5x9.fsf@gnu.org> References: <83o8kkb2vr.fsf@gnu.org> <83a6w4ar50.fsf@gnu.org> <83imara6v0.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19429"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 44313@debbugs.gnu.org To: Aaron Jensen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 30 20:09:30 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kYZmD-0004wa-S5 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Oct 2020 20:09:29 +0100 Original-Received: from localhost ([::1]:35102 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kYZmC-00062W-Tw for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Oct 2020 15:09:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33672) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kYZln-000629-9V for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 15:09:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48238) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kYZlm-0005j8-6A for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 15:09:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kYZlm-0004mV-0A for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 15:09:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 30 Oct 2020 19:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44313 X-GNU-PR-Package: emacs Original-Received: via spool by 44313-submit@debbugs.gnu.org id=B44313.160408489118317 (code B ref 44313); Fri, 30 Oct 2020 19:09:01 +0000 Original-Received: (at 44313) by debbugs.gnu.org; 30 Oct 2020 19:08:11 +0000 Original-Received: from localhost ([127.0.0.1]:59784 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kYZkx-0004lN-B0 for submit@debbugs.gnu.org; Fri, 30 Oct 2020 15:08:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33166) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kYZkw-0004l7-Jg for 44313@debbugs.gnu.org; Fri, 30 Oct 2020 15:08:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50631) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kYZkr-0005RU-DO; Fri, 30 Oct 2020 15:08:05 -0400 Original-Received: from [176.228.60.248] (port=2723 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kYZkp-0000Hs-5S; Fri, 30 Oct 2020 15:08:05 -0400 In-Reply-To: (message from Aaron Jensen on Fri, 30 Oct 2020 13:55:10 -0500) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:192182 Archived-At: > From: Aaron Jensen > Date: Fri, 30 Oct 2020 13:55:10 -0500 > Cc: 44313@debbugs.gnu.org > > On Fri, Oct 30, 2020 at 1:47 PM Eli Zaretskii wrote: > > That doesn't sound like a frame that is not live, that sounds like a > > frame whose memory was freed. Or a frame pointer that is just > > garbage. > > > > So the question now is: where did that frame pointer come from? > > Good question--how might I debug that next time it happens? I don't know. The code in Fmouse_pixel_position uses the selected-frame, so it is quite strange, to say the least, that this frame could be garbled when you just move the mouse pointer.