From: Stefan Kangas <stefan@marxist.se>
To: David Reitter <david.reitter@gmail.com>
Cc: Alan Third <alan@idiocy.org>,
24581@debbugs.gnu.org,
konrad podczeck <konrad.podczeck@univie.ac.at>
Subject: bug#24581: 25.1 crash in ns_scroll_run after closing a frame
Date: Tue, 11 Aug 2020 18:17:15 -0700 [thread overview]
Message-ID: <CADwFkmmJWzuVNHigj9FXYhdnVgZ3KLE8wqv6ZBBEYQ4ze99_UQ@mail.gmail.com> (raw)
In-Reply-To: <CB8EC9CF-9F5E-4564-80FE-4A18E842DB94@gmail.com> (David Reitter's message of "Sun, 2 Oct 2016 21:55:14 -0400")
David Reitter <david.reitter@gmail.com> writes:
> On Oct 1, 2016, at 4:35 PM, Alan Third <alan@idiocy.org> wrote:
>
>> Is it possible to recompile with NSTRACE turned on so we can see the
>> sequence of NS functions up to a crash?
>
> I think we should do that.
That was almost 4 years ago. Are you still seeing this issue? Did you
ever have the chance to recompile with NSTRACE turned on as suggested by
Alan Third? Thanks.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-12 1:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5457C3AC-EEBA-403F-B27D-6C78F59F9F4A@univie.ac.at>
2016-10-01 14:17 ` bug#24581: 25.1 crash in ns_scroll_run after closing a frame David Reitter
2016-10-01 15:56 ` Eli Zaretskii
2016-10-01 20:35 ` Alan Third
2016-10-03 1:55 ` David Reitter
[not found] ` <CABGBtwmdW+hJRYBHtqH0mRspBadPGpGqoCAcndrFChYGJbMoKw@mail.gmail.com>
2016-10-03 6:59 ` Alan Third
2020-08-12 1:17 ` Stefan Kangas [this message]
2020-08-12 10:22 ` David Reitter
2020-08-13 18:21 ` Win Treese
2020-08-13 18:46 ` Alan Third
2020-08-13 20:51 ` Win Treese
2020-08-14 9:51 ` Robert Pluim
2020-08-14 14:43 ` Win Treese
2020-08-14 20:06 ` Alan Third
2020-08-14 19:58 ` Alan Third
2020-10-10 9:45 ` Alan Third
2020-10-10 16:23 ` Win Treese
2020-10-10 16:26 ` Stefan Kangas
2020-10-11 8:44 ` Alan Third
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmJWzuVNHigj9FXYhdnVgZ3KLE8wqv6ZBBEYQ4ze99_UQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=24581@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=david.reitter@gmail.com \
--cc=konrad.podczeck@univie.ac.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).