Some more information after running "valgrind -v xsane".
On my system "scanimage -L" gives:
device `epson:/dev/sg0' is a Epson Perfection1200 flatbed scanner
Since xsane runs in "slow motion" under valgrind you can see in more
detail what happens as it crashes...
1. xsane box "Scanning for devices" appears
2. same box disappears after a short while (so it found the scanner ok)
3. new box pops up with the title "Histogram Perfection1200" and some rainbox
bars in the middle
4. xsane terminates with a segfault.
The trace from valgrind is attached (in a zip file).
In the file you get a whole lot of these errors
Conditional jump or move depends on uninitialised value(s)
plus a bunch of others until you get to the segfault, which looks like
this:
(xsane:6220): Gtk-CRITICAL **: gtk_accel_label_new: assertion `string
!= NULL' failed
(xsane:6220): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion
`GTK_IS_MISC (misc)' failed
(xsane:6220): Gtk-CRITICAL **: gtk_container_add: assertion
`GTK_IS_WIDGET (widget)' failed
(xsane:6220): Gtk-CRITICAL **: gtk_accel_label_set_accel_widget: assertion
`GTK_IS_ACCEL_LABEL (accel_label)' failed
==6220==
==6220== Invalid read of size 1
==6220== at 0x43D4C91: gtk_widget_show (in
/usr/lib/libgtk-x11-2.0.so.0.800.20)
==6220== by 0x42F7CB5: gtk_menu_item_new_with_label (in
/usr/lib/libgtk-x11-2.0.so.0.800.20)
==6220== by 0x8066CF5: (within /usr/bin/xsane)
==6220== by 0x806FD52: (within /usr/bin/xsane)
==6220== by 0x80B12F5: (within /usr/bin/xsane)
==6220== by 0x80B425F: (within /usr/bin/xsane)
==6220== by 0x80B543A: (within /usr/bin/xsane)
==6220== by 0x4874EA1: __libc_start_main (in
/lib/tls/i686/cmov/libc-2.3.6.so)
==6220== Address 0xD is not stack'd, malloc'd or (recently) free'd
==6220==
==6220== Process terminating with default action of signal 11 (SIGSEGV)
==6220== Access not within mapped region at address 0xD
==6220== at 0x43D4C91: gtk_widget_show (in
/usr/lib/libgtk-x11-2.0.so.0.800.20)
==6220== by 0x42F7CB5: gtk_menu_item_new_with_label (in
/usr/lib/libgtk-x11-2.0.so.0.800.20)
==6220== by 0x8066CF5: (within /usr/bin/xsane)
==6220== by 0x806FD52: (within /usr/bin/xsane)
==6220== by 0x80B12F5: (within /usr/bin/xsane)
==6220== by 0x80B425F: (within /usr/bin/xsane)
==6220== by 0x80B543A: (within /usr/bin/xsane)
==6220== by 0x4874EA1: __libc_start_main (in
/lib/tls/i686/cmov/libc-2.3.6.so)
Apparently we are trying to use a 0x0D as a memory address....
Hope this helps. Toby
** Attachment added: "valgrind trace of failing xsane"
http://librarian.launchpad.net/4243493/xsane-trace.zip
--
SEGV on startup
https://launchpad.net/bugs/37968
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
