From: Eli Zaretskii <eliz@gnu.org>
To: Steven Parkes <smparkes@smparkes.net>
Cc: 11583@debbugs.gnu.org
Subject: bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames
Date: Sun, 03 Jun 2012 17:54:53 +0300 [thread overview]
Message-ID: <83vcj8bg3m.fsf@gnu.org> (raw)
In-Reply-To: <90208527-4A88-4E92-B27B-1A48D8E3646B@smparkes.net>
> From: Steven Parkes <smparkes@smparkes.net>
> Date: Sat, 2 Jun 2012 19:05:05 -0700
> Cc: "11583@debbugs.gnu.org" <11583@debbugs.gnu.org>
>
> Okay, bt all appended, which also has the lisp backtrace in it.
>
> The stack trace isn't all that similar to the last one, so I'm not quite sure what to make of it.
I'm not sure either, but...
> #1 0x00000001001a5c6d in x_free_frame_resources (f=0xb0000000109371a2) at nsterm.m:1164
> dpyinfo = (struct ns_display_info *) 0x10164b720
> #2 0x00000001001a2089 in x_destroy_window (f=0xb0000000109371a2) at nsterm.m:1180
> No locals.
> #3 0x0000000100012a09 in delete_frame (frame=4449145253, force=140734799798688) at frame.c:1343
> kb = (struct kboard *) 0x10058c8b0
> f = (struct frame *) 0x1093091a0
... this looks very strange: the value of f in frame #3 (0x1093091a0),
which looks normal, becomes a preposterous value (0xb0000000109371a2)
in x_destroy_window, which is called by delete_frame via the
delete_frame_hook.
Perhaps some NS expert could tell how this can happen.
next prev parent reply other threads:[~2012-06-03 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 18:48 bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames Steven Parkes
2012-05-29 20:55 ` bug#11584: " Steven Parkes
[not found] ` <handler.11584.B.133834111624627.ack@debbugs.gnu.org>
2012-05-30 1:27 ` bug#11584: Acknowledgement (24.0.97; 24 pretest Emacs.app crashes closing frames) Steven Parkes
2012-05-30 2:52 ` bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames Eli Zaretskii
2012-05-30 3:07 ` Steven Parkes
2012-05-30 15:11 ` Eli Zaretskii
2012-05-30 15:45 ` Steven Parkes
2012-06-03 2:05 ` Steven Parkes
2012-06-03 14:54 ` Eli Zaretskii [this message]
2012-06-04 20:30 ` Steven Parkes
2012-06-04 21:09 ` Jan Djärv
2012-06-04 21:11 ` Steven Parkes
2012-06-11 16:57 ` Jan Djärv
2012-06-11 17:31 ` Andreas Schwab
2012-06-12 2:52 ` Steven Parkes
2012-07-14 9:10 ` bug#7879: 24.0.50; Wish: Make c-defun-name recognize objc-methods Jan Djärv
[not found] ` <handler.11583.B.133834111324619.ack@debbugs.gnu.org>
2012-07-02 20:43 ` bug#11583: (24.0.97; 24 pretest Emacs.app crashes closing frames) Steven Parkes
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=83vcj8bg3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11583@debbugs.gnu.org \
--cc=smparkes@smparkes.net \
/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).