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 13:29:31 +0200 Message-ID: <83a6w4ar50.fsf@gnu.org> References: <83o8kkb2vr.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12054"; 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 12:30:10 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 1kYSbi-00031B-9T for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Oct 2020 12:30:10 +0100 Original-Received: from localhost ([::1]:50354 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kYSbg-0005h5-Or for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Oct 2020 07:30:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35528) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kYSba-0005gz-V1 for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 07:30:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44765) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kYSba-0007EW-KS for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 07:30:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kYSba-0006oT-FB for bug-gnu-emacs@gnu.org; Fri, 30 Oct 2020 07:30: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 11:30:02 +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.160405739726153 (code B ref 44313); Fri, 30 Oct 2020 11:30:02 +0000 Original-Received: (at 44313) by debbugs.gnu.org; 30 Oct 2020 11:29:57 +0000 Original-Received: from localhost ([127.0.0.1]:56311 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kYSbV-0006nl-0I for submit@debbugs.gnu.org; Fri, 30 Oct 2020 07:29:57 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35412) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kYSbT-0006nZ-H7 for 44313@debbugs.gnu.org; Fri, 30 Oct 2020 07:29:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39322) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kYSbO-00077j-6P; Fri, 30 Oct 2020 07:29:50 -0400 Original-Received: from [176.228.60.248] (port=2057 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kYSbM-0005gL-Lp; Fri, 30 Oct 2020 07:29:49 -0400 In-Reply-To: (message from Aaron Jensen on Fri, 30 Oct 2020 05:16:35 -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:192056 Archived-At: > From: Aaron Jensen > Date: Fri, 30 Oct 2020 05:16:35 -0500 > Cc: 44313@debbugs.gnu.org > > > if (f && FRAME_NS_P (f)) > > > > So why does FRAME_NS_P crash? which part of the frame's structure are > > invalid? > > I believe that macro is defined as: > > #define FRAME_NS_P(f) ((f)->output_method == output_ns) > > Would the de-reference cause an EXC_BAD_ACCESS if the frame had been released? If f is non-NULL, I don't think it could case EXC_BAD_ACCESS, unless f is garbled and points outside of the process's address space. Which is why we need to see the value of f and whether the address it points to could be accessed. > I make use of child frames via the posframe packages. I wonder if > something requested a mouse pixel position for a frame either as it > was being released or after it was being released? For this, we need to see the Lisp-level backtrace at the crash. Sadly, AFAIK lldb doesn't support the commands in src/.gdbinit, so the only way to generate this I know of is to manually show the function called by each Funcall in the C backtrace. Which is quite tedious.