all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gordon Farquharson <gordonfarquharson@gmail.com>
Cc: 18997@debbugs.gnu.org
Subject: bug#18997: 24.4; IDLWAVE: Emacs crashes when trying to change the window while in the IDL shell
Date: Sat, 14 Nov 2015 12:30:11 +0200	[thread overview]
Message-ID: <83bnaweuvg.fsf@gnu.org> (raw)
In-Reply-To: <CABwPwwKVtuR9+r+BKiTEOiFJv5sM4=i0RxQwwkRh-hBc_q8rpA@mail.gmail.com>

> Date: Fri, 13 Nov 2015 08:52:29 -0800
> From: Gordon Farquharson <gordonfarquharson@gmail.com>
> Cc: Glenn Morris <rgm@gnu.org>, 18997@debbugs.gnu.org
> 
>     See gud-tool-bar-map and its uses. As you see, GUD uses a very
>     different method.
> 
> I'll take a look. I've never programmed in elisp. The closest related language
> I've used is scheme, a very long time ago, so this will be exciting.

I think on the Lisp level everything is OK.  Fact is, this worked
before the changes in GTK toolbar support mentioned previously in
discussing this thread.  It also works with other toolkits (Glenn
mentioned Lucid, I see it display correctly on MS-Windows).

So I think a better strategy would be to step in a debugger through
the offending C code and see the differences between when IDLWAVE is
invoked, and when GUD is invoked.  You can identify the code that's
involved in this by examining the series of functions that crash.
Based on the Glib error messages posted up-thread, I would suggest to
start in xg_get_pixbuf_from_pixmap, which calls
gdk_pixbuf_new_from_data, the first function to complain.  How is the
data there different between GUD and IDLWAVE?





  reply	other threads:[~2015-11-14 10:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 13:27 bug#18997: 24.4; IDLWAVE: Emacs crashes when trying to change the window while in the IDL shell Mosè Giordano
2015-09-22  6:48 ` Jonathan Woithe
2015-11-11 22:48 ` Gordon Farquharson
2015-11-11 23:18   ` Gordon Farquharson
2015-11-12 16:13   ` Eli Zaretskii
2015-11-12 17:55     ` Glenn Morris
2015-11-12 18:04       ` Glenn Morris
2015-11-12 18:20         ` Eli Zaretskii
2015-11-12 18:24           ` Glenn Morris
2015-11-12 18:33             ` Eli Zaretskii
2015-11-12 18:38               ` Gordon Farquharson
2015-11-12 18:44                 ` Eli Zaretskii
2015-11-12 18:54                   ` Gordon Farquharson
2015-11-12 19:33                     ` Eli Zaretskii
2015-11-12 20:20                       ` Gordon Farquharson
2015-11-12 20:35                 ` Gordon Farquharson
2015-11-12 20:52                   ` Eli Zaretskii
2015-11-12 21:41                     ` Gordon Farquharson
2015-11-12 21:57                       ` Gordon Farquharson
2015-11-12 22:05                         ` Gordon Farquharson
2015-11-13  8:33                         ` Eli Zaretskii
2015-11-13 16:52                           ` Gordon Farquharson
2015-11-14 10:30                             ` Eli Zaretskii [this message]
2015-11-12 18:29         ` Gordon Farquharson
2015-11-12 18:16       ` Eli Zaretskii
2015-11-12 18:24         ` Glenn Morris
     [not found]         ` <CABwPwwJZVsdZxPPKdoysZbbQ4wuDx5pTdworGoX91Q92EyxyVA@mail.gmail.com>
2015-11-12 18:32           ` Eli Zaretskii
2015-11-12 18:35             ` Gordon Farquharson
2015-11-12 18:33         ` Gordon Farquharson
2016-03-25  0:04 ` Paul Eggert
2016-03-25 11:26   ` Mosè Giordano
2016-03-28 22:49   ` JD Smith
2016-03-29  6:47   ` Jonathan Woithe

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=83bnaweuvg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18997@debbugs.gnu.org \
    --cc=gordonfarquharson@gmail.com \
    /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.