Re: [Bug: 21.4.21] Segfault on reading png
On Thu, 26 Jun 2008 23:39:48 +0200, Aidan wrote:
I would be super-interested in the values of ximage, of ximage->f,
and
of ximage-> f.destroy_image in that stack frame. You’ll need to do
something like the following within GDB to have that shown:
(gdb) up 6
(gdb) p ximage
(gdb) p ximage->f
(gdb) p ximage->f.destroy_image
up 6 didn't work ('No symbol "ximage" in current context.'), so I
tried
up 5 instead and got this (complete output included at the bottom):
(gdb) up 5
#5 0x00000000005d434c in x_init_image_instance_from_eimage (ii=0xdb0160, width=63,
height=19, slices=1,
eimage=0xdcf120
"âáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáäâáä}}{âáäâáäâáäâá"...,
dest_mask=-1,
instantiator=13493120, domain=13403264) at glyphs-x.c:988
988 XDestroyImage (ximage);
(gdb) p ximage
$1 = (XImage *) 0xdc91f0
(gdb) p ximage->f
$2 = {create_image = 0x7f8c7e147e10 <XCreateImage>, destroy_image = 0x7f8c7e1481b0,
get_pixel = 0x7f8c7e147570,
put_pixel = 0x7f8c7e147880, sub_image = 0x7f8c7e147ff0, add_pixel = 0x7f8c7e147c90}
(gdb) p ximage->f.destroy_image
$3 = (int (*)(struct _XImage *)) 0x7f8c7e1481b0
Thanks for investigating this,
Thank you for that! :-)
Best regards,
Adam
== full output: ==
$ ulimit -c unlimited
$ xemacs --vanilla /usr/lib/xemacs-21.4.21/etc/custom/reset-up.png
Warning: Missing charsets in String to FontSet conversion
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway. Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu. If necessary, send
ordinary email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.
*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem. Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x99b228) 0x9c39d0>
...)
# (unwind-protect ...)
make-image-instance([png :data "�©PNG\n\n