Your message dated Fri, 23 Jan 2009 17:15:26 +0100
with message-id <1232727326.8632.39.ca...@tomoyo>
and subject line Re: Bug#332182: libgtk2.0-0: valgrind reports errors inside 
gtk/gdk/glib
has caused the Debian Bug report #332182,
regarding libgdk-pixbuf2: invalid read in gdkpixbuf module loading (dlopen?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
332182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgdk-pixbuf2
Version: 0.22.0-11
Severity: important


Running a program that uses gdkpixbuf (in this case, freeciv 2.1) under
valgrind reveals numerous memory errors.  These all happen inside 
_gdk_pixbuf_load_module.  For instance:

==30756== Invalid read of size 4
==30756==    at 0x4010FB9: (within /lib/ld-2.3.5.so)
==30756==    by 0x400AFA9: (within /lib/ld-2.3.5.so)
==30756==    by 0x4007DBD: (within /lib/ld-2.3.5.so)
==30756==    by 0x490DEA8: do_sym (dl-sym.c:113)
==30756==    by 0x490E0EB: _dl_sym (dl-sym.c:154)
==30756==    by 0x45F2E60: dlsym_doit (dlsym.c:51)
==30756==    by 0x400B056: (within /lib/ld-2.3.5.so)
==30756==    by 0x45F32FF: _dlerror_run (dlerror.c:162)
==30756==    by 0x45F2EC0: dlsym (dlsym.c:71)
==30756==    by 0x45F039E: g_module_symbol (in 
/usr/lib/libgmodule-2.0.so.0.800.5)
==30756==    by 0x45F08CF: g_module_open (in 
/usr/lib/libgmodule-2.0.so.0.800.5)==30756==    by 0x43E8593: 
_gdk_pixbuf_load_module (gdk-pixbuf-io.c:456)
==30756==    by 0x43E8E61: gdk_pixbuf_new_from_file (gdk-pixbuf-io.c:883)
==30756==    by 0x81473C4: load_gfxfile (sprite.c:197)
==30756==    by 0x808754E: load_gfx_file (tilespec.c:1011)
==30756==    by 0x8087680: ensure_big_sprite (tilespec.c:1050)
==30756==    by 0x8089901: load_sprite (tilespec.c:1698)
==30756==    by 0x808A25D: tileset_lookup_sprite_tags (tilespec.c:1979)
==30756==    by 0x808D881: tileset_load_tiles (tilespec.c:2468)
==30756==    by 0x812A4A1: ui_main (gui_main.c:1314)
==30756==    by 0x8059C33: main (civclient.c:378)
==30756==  Address 0x53B6E94 is 52 bytes inside a block of size 54 alloc'd
==30756==    at 0x401B41A: malloc (vg_replace_malloc.c:149)
==30756==    by 0x4003D27: (within /lib/ld-2.3.5.so)
==30756==    by 0x40064DA: (within /lib/ld-2.3.5.so)
==30756==    by 0x490BE70: dl_open_worker (dl-open.c:259)
==30756==    by 0x400B056: (within /lib/ld-2.3.5.so)
==30756==    by 0x490C754: _dl_open (dl-open.c:577)
==30756==    by 0x45F2D2E: dlopen_doit (dlopen.c:59)
==30756==    by 0x400B056: (within /lib/ld-2.3.5.so)
==30756==    by 0x45F32FF: _dlerror_run (dlerror.c:162)
==30756==    by 0x45F2D9C: dlopen@@GLIBC_2.1 (dlopen.c:78)
==30756==    by 0x45F05C0: g_module_open (in 
/usr/lib/libgmodule-2.0.so.0.800.5)==30756==    by 0x43E8593: 
_gdk_pixbuf_load_module (gdk-pixbuf-io.c:456)
==30756==    by 0x43E8E61: gdk_pixbuf_new_from_file (gdk-pixbuf-io.c:883)
==30756==    by 0x81473C4: load_gfxfile (sprite.c:197)
==30756==    by 0x808754E: load_gfx_file (tilespec.c:1011)
==30756==    by 0x8087680: ensure_big_sprite (tilespec.c:1050)
==30756==    by 0x8089901: load_sprite (tilespec.c:1698)
==30756==    by 0x808A25D: tileset_lookup_sprite_tags (tilespec.c:1979)
==30756==    by 0x808D881: tileset_load_tiles (tilespec.c:2468)
==30756==    by 0x812A4A1: ui_main (gui_main.c:1314)
==30756==    by 0x8059C33: main (civclient.c:378)

In this case the malloc simply isn't big enough, or perhaps the read is in
the wrong place.  This is a bizarre and fairly serious error, I suspect.

I don't really know that this error is caused by gdkpixbuf; it could be
directly within the dl code.  However the dl functions do not have symbol
information it seems, and I don't know why (I have libc6-dbg installed).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages libgdk-pixbuf2 depends on:
ii  libc6                         2.3.5-11   GNU C Library: Shared libraries an
ii  libgtk1.2                     1.2.10-18  The GIMP Toolkit set of widgets fo
ii  libjpeg62                     6b-11      The Independent JPEG Group's JPEG 
ii  libpng12-0                    1.2.8rel-5 PNG library - runtime
ii  libtiff4                      3.7.4-1    Tag Image File Format (TIFF) libra

libgdk-pixbuf2 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.12.11-3

Le vendredi 12 décembre 2008 à 22:18 +0100, Luca Bruno a écrit :
> Confirming no errors in lenny.
> Please consider retrying [1]:
> G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck 
> --leak-resolution=high --num-callers=20 ./testprogram
> 
> For what concerns the fgbgmodifier.c, I think a new bug with lower severity
> might be more suitable. This one refers to errors not memory leaks.

Thanks for checking, I’m closing the bug.

-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée


--- End Message ---

Reply via email to