[Bug 909567] New: scangearmp2 produces segfault in libpthread-2.18.so
http://bugzilla.opensuse.org/show_bug.cgi?id=909567 Bug ID: 909567 Summary: scangearmp2 produces segfault in libpthread-2.18.so Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Commercial Assignee: bnc-team-screening@forge.provo.novell.com Reporter: martin.gu@intergga.ch QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 Build Identifier: The application scangearmp2 is downloaded from http://de.canon.ch/Support/Consumer_Products/products/Fax__Multifunctionals/InkJet/PIXMA_MG_series/PIXMA_MG7550.aspx?type=download&language=&os=Linux Installation with YaST or install.sh does not produce any error. But a start results in a memory access error. dmesg shows scangearmp2[9080]: segfault at 30 ip 00007fa0cf0f1294 sp 00007ffff2277a20 error 4 in libpthread-2.18.so[7fa0cf0e7000+18000] This error occurres with or withour a Canon Pixma MG7550 attached / switched on. Reproducible: Always Steps to Reproduce: 1.install scangearmp2 2.run scangearmp2 3. Actual Results: Application crashes with error message "Speicherzugriffsfehler" (memory access error) Expected Results: The application should be up and running, allowing to scan images I reported the error to Canon but I was informed that this is an error of the distribution (in libpthread-2.18.so) and that I should get help there. Unfortunately SANE does not yet support the Canon pixma MG7550 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=909567
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=909567
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=909567
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=909567
--- Comment #5 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=909567
http://bugzilla.opensuse.org/show_bug.cgi?id=909567#c7
Ralf Habacker
With probability one (http://en.wikipedia.org/wiki/Almost_surely) when there is a segfault in a glibc library function the root cause is not in the library itself but at a higher level somewhere in the application that calls library functions in a wrong way (usually by calling a library function with an invalid pointer argumet - i.e. the caller provides an invalid argumet and that causes the segfault).
I can confirm this: the call to numdev = libusb_get_device_list(NULL, &g_devlist); does not use the predefined libusb context pointer and should be numdev = libusb_get_device_list(g_context, &g_devlist); which solves the issue. See https://github.com/Ordissimo/scangearmp2/issues/16 for more details -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com