Package: ufraw Version: 0.4+cvs20050818-1 Followup-For: Bug #327902
I believe this is caused by a compiler problem. The default CFLAGS include -O3 and -O2. When I take out -O3 and -O2 from the compiler flags, ufraw behaves as expected. This is with gcc 4.0.2. gcc 3.4.5 works as expected with the default CFLAGS. Stepping through the program (gcc-4.0.2 w/ -O2,-O3), when execution hits ufraw_exif.c:100, it immediately proceeds to line 264, which is a bit suspicious... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (1000, 'unstable'), (750, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages ufraw depends on: ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libc6 2.3.5-7 GNU C Library: Shared libraries an ii libexif12 0.6.12-2 library to parse EXIF files ii libgimp2.0 2.2.8-11 Libraries necessary to Run the GIM ii libglib2.0-0 2.8.3-1 The GLib library of C routines ii libgtk2.0-0 2.6.10-1 The GTK+ graphical user interface ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii liblcms1 1.13-1 Color management library ii libpango1.0-0 1.8.2-3 Layout and rendering of internatio ii libtiff4 3.7.4-1 Tag Image File Format (TIFF) libra ii zlib1g 1:1.2.3-4 compression library - runtime ufraw recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
