unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: crash in cvs head
Date: Fri, 30 Jun 2006 23:21:45 -0400	[thread overview]
Message-ID: <E1FwW3F-0004EE-En@fencepost.gnu.org> (raw)
In-Reply-To: <alwtb0uhqc.fsf@quant8.janestcapital.quant> (message from Sam Steingold on Thu, 29 Jun 2006 11:03:23 -0400)

    (gdb) p dpyinfo
    $1 = (struct x_display_info *) 0x0
    (gdb) up
    #1  0x080cedf4 in unwind_create_frame (frame=193660300) at xfns.c:2968
    2968          x_free_frame_resources (f);
    (gdb) p f
    No symbol "f" in current context.

The variable f was apparently optimized away.
It was surely created from FRAME.  If you had examined the data inside
FRAME, you could have diagnosed more.

Nonetheless, I think I see the problem.  Does this fix it?


*** xfns.c	25 Jun 2006 12:16:32 -0400	1.668
--- xfns.c	30 Jun 2006 15:46:37 -0400	
***************
*** 3075,3081 ****
    f->output_data.x->scroll_bar_top_shadow_pixel = -1;
    f->output_data.x->scroll_bar_bottom_shadow_pixel = -1;
  #endif /* USE_TOOLKIT_SCROLL_BARS */
-   record_unwind_protect (unwind_create_frame, frame);
  
    f->icon_name
      = x_get_arg (dpyinfo, parms, Qicon_name, "iconName", "Title",
--- 3075,3080 ----
***************
*** 3084,3089 ****
--- 3083,3091 ----
      f->icon_name = Qnil;
  
    FRAME_X_DISPLAY_INFO (f) = dpyinfo;
+ 
+   /* With FRAME_X_DISPLAY_INFO set up, this unwind-protect is safe.  */
+   record_unwind_protect (unwind_create_frame, frame);
  #if GLYPH_DEBUG
    image_cache_refcount = FRAME_X_IMAGE_CACHE (f)->refcount;
    dpyinfo_refcount = dpyinfo->reference_count;

  reply	other threads:[~2006-07-01  3:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 15:03 crash in cvs head Sam Steingold
2006-07-01  3:21 ` Richard Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-18 13:07 Sam Steingold
2006-10-20 13:17 ` Sam Steingold
2006-10-23  9:59   ` Kim F. Storm
2006-03-06 19:08 Sam Steingold
2006-03-07  4:38 ` Eli Zaretskii
2003-02-21  0:47 Crash in CVS head Kim F. Storm

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=E1FwW3F-0004EE-En@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).