unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: tobias.getzner@gmx.de, 20802@debbugs.gnu.org
Subject: bug#20802: Segfault when showing non-GTK+ tooltip
Date: Sat, 13 Jun 2015 17:01:44 +0300	[thread overview]
Message-ID: <83vberpv07.fsf@gnu.org> (raw)
In-Reply-To: <557C2EF2.5030308@gmx.at>

> Date: Sat, 13 Jun 2015 15:24:02 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: tobias.getzner@gmx.de, 20802@debbugs.gnu.org
> 
>  > Thanks, but I still cannot reproduce this.  (On what OS did you
>  > reproduce it?)
> 
> A Gtk build on Debian.  Run with all my customizations.

I see that x_decode_color in xfns.c signals an error, while the same
function in w32fns.c doesn't.  But even if I add the call to
signal_error to w32fns.c's implementation, I still cannot reproduce
the crash.  I do see an error message in the echo area, but no
debugger pops up.

> Sorry, I forgot to tell.  Line 1775 of image.c here is
> 
>    for (i = 0; i < c->used; ++i)
> 
> in the context of
> 
>    struct image_cache *c = FRAME_IMAGE_CACHE (f);
>    ptrdiff_t i;
> 
>    /* Find a free slot in c->images.  */
>    for (i = 0; i < c->used; ++i)
>      if (c->images[i] == NULL)
>        break;
> 
>    /* If no free slot found, maybe enlarge c->images.  */
> 
> in cache_image.  i is still 0 and I get
> 
> (gdb) p c->used
> Cannot access memory at address 0x18

So FRAME_IMAGE_CACHE returns a NULL pointer, I guess.  But how did
that happen?  We allocate the cache in xfaces.c:init_frame_faces.  I
could understand why init_frame_faces was not yet called for the tip
frame we were trying to create, but the crash happens because of a
different frame.  Look:

  #37 0x000000000054c091 in x_decode_color (f=0x24d2c30, color_name=..., mono_color=16777215) at ../../src/xfns.c:495
  #38 0x000000000054c566 in x_set_background_color (f=0x24d2c30, arg=..., oldval=...) at ../../src/xfns.c:638
  #39 0x000000000042d45d in x_set_frame_parameters (f=0x24d2c30, alist=...) at ../../src/frame.c:3152
  #40 0x0000000000431ce6 in x_default_parameter (f=0x24d2c30, alist=..., prop=..., deflt=..., xprop=0x6fd49d "background", xclass=0x6fd908 "Background", type=RES_TYPE_STRING) at ../../src/frame.c:4374
  #41 0x000000000055549d in x_create_tip_frame (dpyinfo=0x1621ee0, parms=..., text=...) at ../../src/xfns.c:5173

This is the tip frame we are creating, its pointer is 0x24d2c30.  But
when we crash, it's for a different frame, whose pointer is 0x13a7e00:

  #0  0x00000000006c9b5c in cache_image (f=0x13a7e00, img=0x249e010) at ../../src/image.c:1775
  #1  0x00000000006c96e3 in lookup_image (f=0x13a7e00, spec=...) at ../../src/image.c:1686

Can you see what is that frame, and why we didn't call
init_frame_faces for it?  Also, which image are we trying to display
here?  Something on the toolbar, perhaps?  Did you move mouse pointer
over a tool-bar button to trigger a tooltip that failed?





  reply	other threads:[~2015-06-13 14:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13  9:18 bug#20802: Segfault when showing non-GTK+ tooltip Tobias Getzner
2015-06-13  9:38 ` Eli Zaretskii
2015-06-13 10:25   ` martin rudalics
2015-06-13 10:54     ` Eli Zaretskii
2015-06-13 13:24       ` martin rudalics
2015-06-13 14:01         ` Eli Zaretskii [this message]
2015-06-13 14:28           ` martin rudalics
2015-06-13 14:42             ` Eli Zaretskii
2015-06-14 11:00               ` martin rudalics
2015-06-14 14:12                 ` Eli Zaretskii
2015-06-15  8:22                   ` martin rudalics
2015-06-15 15:01                     ` Eli Zaretskii
2015-06-15 16:00                       ` martin rudalics
2015-06-15 17:29                         ` Eli Zaretskii
2015-06-16 13:30                           ` martin rudalics
2015-06-16 14:54                             ` Eli Zaretskii
2015-06-17  9:36                   ` martin rudalics
2015-06-17 16:39                     ` Eli Zaretskii
2015-06-17 18:56                       ` Stefan Monnier
2015-06-18 13:37                       ` martin rudalics
2015-06-18 15:53                         ` Eli Zaretskii
2015-06-18 16:48                           ` martin rudalics
2015-06-18 17:17                             ` Eli Zaretskii
2015-06-18 17:36                               ` martin rudalics
2015-06-18 18:00                                 ` Eli Zaretskii
2015-06-19  6:43                                   ` martin rudalics
2022-04-29 11:45     ` Lars Ingebrigtsen
2022-05-28 10:58       ` Lars Ingebrigtsen
2015-06-16  7:21   ` Tobias Getzner
2015-06-16 13:30     ` martin rudalics
2015-06-16 15:34       ` Tobias Getzner
2015-06-16 15:58         ` Eli Zaretskii
2015-06-16 16:34           ` Tobias Getzner
2015-06-16 17:12             ` Eli Zaretskii
2015-06-16 17:31             ` martin rudalics
2015-06-17  7:34               ` Tobias Getzner
2015-06-17  8:04                 ` martin rudalics
2015-06-17 14:11                   ` Tobias Getzner
2015-06-18 13:37                     ` martin rudalics
2015-06-18 14:09                       ` Tobias Getzner
2015-06-17 16:30                 ` Eli Zaretskii

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=83vberpv07.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20802@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=tobias.getzner@gmx.de \
    /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).