scanimage crashed with SIGSEGV in memchr()

Bug #1224764 reported by pqwoerituytrueiwoq
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

clearly still unstable

chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' is a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' is a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -f "{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$ scanimage -f "{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:004:002","NAME":"UMAX 3400 flatbed scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard Deskjet_F4400_series all-in-one"},chad@chad-VirtualBox:~$ ^C
chad@chad-VirtualBox:~$ scanimage -f "{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: sane-utils 1.0.23-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Thu Sep 12 22:56:32 2013
ExecutablePath: /usr/bin/scanimage
InstallationDate: Installed on 2013-07-27 (47 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
MarkForUpload: True
ProcCmdline: scanimage -f {"ID":%i,"INUSE":0,"DEVICE":"%d","NAME":"%v\ %m\ %t"},
SegvAnalysis:
 Segfault happened at: 0x7f462dca8e20 <memchr+192>: movdqa (%rdi),%xmm0
 PC (0x7f462dca8e20) ok
 source "(%rdi)" (0x7f462e40a000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: sane-backends
StacktraceTop:
 memchr () at ../sysdeps/x86_64/memchr.S:88
 __GI__IO_getline_info (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1023, delim=delim@entry=10, extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
 __GI__IO_getline (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1023, delim=delim@entry=10, extract_delim=extract_delim@entry=1) at iogetline.c:38
 __GI_fgets_unlocked (buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1024, fp=0x688950) at iofgets_u.c:55
 internal_getent (result=result@entry=0x7f462179d530, buffer=buffer@entry=0x7f462179d100 "z3950", buflen=buflen@entry=1024, errnop=errnop@entry=0x7f462179e680) at nss_files/files-XXX.c:207
Title: scanimage crashed with SIGSEGV in memchr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
pqwoerituytrueiwoq (pqwoerituytrueiwoq) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 memchr () at ../sysdeps/x86_64/memchr.S:88
 __GI__IO_getline_info (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1023, delim=delim@entry=10, extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
 __GI__IO_getline (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1023, delim=delim@entry=10, extract_delim=extract_delim@entry=1) at iogetline.c:38
 __GI_fgets_unlocked (buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1024, fp=0x688950) at iofgets_u.c:55
 internal_getent (result=result@entry=0x7f462179d530, buffer=buffer@entry=0x7f462179d100 "z3950", buflen=buflen@entry=1024, errnop=errnop@entry=0x7f462179e680) at nss_files/files-XXX.c:207

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in sane-backends (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sane-backends (Ubuntu):
status: New → Confirmed
Revision history for this message
Tuomas Suutari (tuomas-suutari) wrote :
Download full text (4.7 KiB)

Same here. Kubuntu 13.10

Here's a backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 22748]
memchr () at ../sysdeps/x86_64/memchr.S:39
39 ../sysdeps/x86_64/memchr.S: No such file or directory.
(gdb) bt
#0 memchr () at ../sysdeps/x86_64/memchr.S:39
#1 0x00007ffff787a267 in __GI__IO_getline_info (fp=fp@entry=0x7fffe4001370, buf=buf@entry=0x7fffeb3898f0 "kazaa", n=n@entry=2047, delim=delim@entry=10, extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
#2 0x00007ffff787a398 in __GI__IO_getline (fp=fp@entry=0x7fffe4001370, buf=buf@entry=0x7fffeb3898f0 "kazaa", n=n@entry=2047, delim=delim@entry=10, extract_delim=extract_delim@entry=1) at iogetline.c:38
#3 0x00007ffff787ecbc in __GI_fgets_unlocked (buf=buf@entry=0x7fffeb3898f0 "kazaa", n=n@entry=2048, fp=0x7fffe4001370) at iofgets_u.c:55
#4 0x00007fffea98265d in internal_getent (result=result@entry=0x7fffeb38a530, buffer=buffer@entry=0x7fffeb3898f0 "kazaa", buflen=buflen@entry=2048, errnop=errnop@entry=0x7fffeb38b680) at nss_files/files-XXX.c:207
#5 0x00007fffea982a44 in _nss_files_getservbyname_r (name=0x7fffeb9f8812 "sane-port", proto=0x7ffff798a03e <gaih_inet_typeproto+30> "tcp", result=0x7fffeb38a530, buffer=0x7fffeb3898f0 "kazaa", buflen=2048, errnop=0x7fffeb38b680) at nss_files/files-service.c:41
#6 0x00007ffff7920bc2 in __getservbyname_r (name=name@entry=0x7fffeb9f8812 "sane-port", proto=proto@entry=0x7ffff798a03e <gaih_inet_typeproto+30> "tcp", resbuf=resbuf@entry=0x7fffeb38a530, buffer=buffer@entry=0x7fffeb3898f0 "kazaa", buflen=buflen@entry=2048,
    result=result@entry=0x7fffeb38a520) at ../nss/getXXbyYY_r.c:266
#7 0x00007ffff78d62cb in gaih_inet_serv (servicename=0x7fffeb9f8812 "sane-port", tp=tp@entry=0x7ffff798a034 <gaih_inet_typeproto+20>, st=st@entry=0x7fffeb38a5b0, req=<optimised out>) at ../sysdeps/posix/getaddrinfo.c:164
#8 0x00007ffff78d6633 in gaih_inet (name=name@entry=0x7fffe4001138 "kuutio.local", service=0x7fffeb38a7f0, req=req@entry=0x7fffeb38a950, pai=pai@entry=0x7fffeb38a7b0, naddrs=naddrs@entry=0x7fffeb38a790) at ../sysdeps/posix/getaddrinfo.c:341
#9 0x00007ffff78da914 in __GI_getaddrinfo (name=0x7fffe4001138 "kuutio.local", service=<optimised out>, hints=0x7fffeb38a950, pai=0x7fffeb38a948) at ../sysdeps/posix/getaddrinfo.c:2473
#10 0x00007fffeb9f4c3c in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1
#11 0x00007fffeb9f4f48 in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1
#12 0x00007fffeb5da5db in avahi_service_resolver_event () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#13 0x00007fffeb5d5ecc in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#14 0x00007fffeb39a9e6 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#15 0x00007fffeb5dc606 in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#16 0x00007fffeb7e9668 in avahi_simple_poll_dispatch () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#17 0x00007fffeb7e994d in avahi_simple_poll_loop () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#18 0x00007fffeb7e9a14 in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#19 0x00007ffff6ab1f6e in start_thread (arg=0x7fffe...

Read more...

Revision history for this message
Tuomas Suutari (tuomas-suutari) wrote :

If I stop avahi daemon at the Sane server, the segfault goes away.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.