From: Anders Lindgren <andlind@gmail.com>
To: ivan.cibrario@polito.it, 23462@debbugs.gnu.org,
Alan Third <alan@idiocy.org>
Subject: bug#23462: 25.0.93; Crash on OS X when suspending main frame
Date: Tue, 10 May 2016 20:56:51 +0200 [thread overview]
Message-ID: <CABr8ebZPJ1fb=WSaNK6T-n8aBnV4h_=YesMUnfTdukHM520Jww@mail.gmail.com> (raw)
In-Reply-To: <34370B08-B94B-41A9-A9B7-EA3F39EBE900@polito.it>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Hi Ivan and Alan!
I'm not sure that is the correct place for the patch.
Could you enable NSTRACE (by uncommenting the line defining NSTRACE_ENABLED
in nsterm.h) and see which function calls `drawRect` (if possible). If that
is in a function that is part of Emacs, it's better to check that the frame
is visible higher up in the call chain.
You will have to start Emacs from a terminal window in order to see the
trace output. You can do this by running
"./nextstep/Emacs.app/Content/MacOS/Emacs".
-- Anders
[-- Attachment #2: Type: text/html, Size: 668 bytes --]
next prev parent reply other threads:[~2016-05-10 18:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:25 bug#23462: 25.0.93; Crash on OS X when suspending main frame Ivan Cibrario Bertolotti
2016-05-08 9:53 ` Alan Third
2016-05-08 15:58 ` Eli Zaretskii
2016-05-08 16:56 ` Ivan Cibrario Bertolotti
2016-05-08 22:41 ` Alan Third
2016-05-09 8:49 ` Ivan Cibrario Bertolotti
2016-05-10 18:56 ` Anders Lindgren [this message]
2016-05-10 20:13 ` Ivan Cibrario Bertolotti
2016-05-10 21:57 ` Anders Lindgren
2016-05-10 22:08 ` Alan Third
2016-05-10 23:16 ` Alan Third
2016-05-11 22:28 ` Alan Third
2016-05-12 5:39 ` Anders Lindgren
2016-05-12 11:52 ` bug#23462: [PATCH] Block input while minimizing on NS (bug#23462) Alan Third
2016-05-12 16:38 ` Ivan Cibrario Bertolotti
2016-05-12 18:28 ` Anders Lindgren
2016-05-16 18:45 ` Anders Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABr8ebZPJ1fb=WSaNK6T-n8aBnV4h_=YesMUnfTdukHM520Jww@mail.gmail.com' \
--to=andlind@gmail.com \
--cc=23462@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=ivan.cibrario@polito.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.