Re: [sane-devel] UsbSnoop for Canon DR-C225
my scripts currently don't handle having this kind of mixed data in one log. I could update them I suppose, but it would be easier to get a smaller log- can you try bypassing the hub when making the log? Connect the scanner directly to the machine? allan On Mon, Mar 30, 2015 at 10:06 PM, Nicolas Marchildon nico...@marchildon.net wrote: This is on Windows XP. For some reason, I was not capturing anything until I included the USB hub *and* the scanner. Is the log worthless? Le lun. 30 mars 2015 à 21:33, m. allan noah kitno...@gmail.com a écrit : Your log has the packets from two different devices in it, or something else strange is going on. What OS was this captured on? allan On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah kitno...@gmail.com wrote: have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] UsbSnoop for Canon DR-C225
This is on Windows XP. For some reason, I was not capturing anything until I included the USB hub *and* the scanner. Is the log worthless? Le lun. 30 mars 2015 à 21:33, m. allan noah kitno...@gmail.com a écrit : Your log has the packets from two different devices in it, or something else strange is going on. What OS was this captured on? allan On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah kitno...@gmail.com wrote: have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Raspbian Jessie - scanbd scripting issue
Am 31.03.2015 um 15:43 schrieb RainerF:
Wilhelm,
thank you for taking the time to look into these issues. Following your
advise I had a look into the source code and tried to understand, what
happens in case, when e.g. button 3 is pressed and compared the logs
with the information by pressing e.g. button 4 (log file excerpt - see
below).
The last common action for both button events is this logging information:
scanbd: button 4 has been pressed.
respective
scanbd: button 3 has been pressed.
The message has been generated in file scanbuttond_wrapper.c in line 519
(source version 1.4.2). Next follows this if statement:
Ok, re-looking at these lines I would say its a bug!
As I said before with the scanbuttond-backends there is no change for
the button values from from_value to to_value. Its only pressed/not-pressed.
So please change the bool-expression in this if() to true
and test, please.
if ((st-opts[si].from_value.num_value == st-opts[si].value.num_value)
(st-opts[si].to_value.num_value == value)) {
slog(SLOG_DEBUG, value trigger: numerical);
st-triggered = true;
st-triggered_option = si;
// we need to trigger all waiting threads
if (pthread_cond_broadcast(st-cv) 0) {
slog(SLOG_ERROR, pthread_cond_broadcats: this shouln't happen);
}
}
Within the if statement the next logging message is generated and a new
thread, where further action for script execution seems to be taken. The
logging information is only printed for button 3! Obviously the if
condition is false for button 4. I will try to debug this (I have no
experience with debugging multi-threaded code), hoping to get closer to
the problem, why no script is executed for button 1 and 4 - or do you
already have an idea, what might be wrong?
Kind regards,
Rainer.
syslog excerpt
button 4 pressed
scanbd: polling thread for Perfection 1670 cancellation point
scanbd: polling device Perfection 1670
scanbd: button 4 pressed
scanbd: option: 1
scanbd: scanbtnd_button_name (1)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option scan number 1 (0) for device Perfection 1670
scanbd: option: 3
scanbd: scanbtnd_button_name (3)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option email number 3 (1) for device Perfection 1670
scanbd: option: 2
scanbd: scanbtnd_button_name (2)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option copy number 2 (2) for device Perfection 1670
scanbd: option: 4
scanbd: scanbtnd_button_name (4)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option pdf number 4 (3) for device Perfection 1670
scanbd: button 4 has been pressed.
scanbd: Iteration on dbus call
scanbd: polling thread for Perfection 1670 cancellation point
scanbd: polling device Perfection 1670
...
button 3 pressed
scanbd: polling thread for Perfection 1670 cancellation point
scanbd: polling device Perfection 1670
scanbd: button 3 pressed
scanbd: option: 1
scanbd: scanbtnd_button_name (1)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option scan number 1 (0) for device Perfection 1670
scanbd: option: 3
scanbd: scanbtnd_button_name (3)
scanbd: scanbtnd_button_name, backend: Snapscan USB
scanbd: checking option email number 3 (1) for device Perfection 1670
scanbd: button 3 has been pressed.
scanbd: value trigger: numerical
scanbd: trigger action for device Perfection 1670 with script scan.script
scanbd: setting env:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
scanbd: No PWD, setting env: PWD=/home/pi
scanbd: setting env: USER=root
scanbd: setting env: HOME=/root
scanbd: setting env: SCANBD_DEVICE=snapscan:libusb:001:004
scanbd: setting env: SCANBD_ACTION=email
scanbd: append string Perfection 1670 to signal scan_begin
scanbd: now sending signal scan_begin
scanbd: Iteration on dbus call
scanbd: append string
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin to signal
trigger
scanbd: append string PWD=/home/pi to signal trigger
scanbd: append string USER=root to signal trigger
scanbd: append string HOME=/root to signal trigger
scanbd: append string SCANBD_DEVICE=snapscan:libusb:001:004 to signal trigger
scanbd: append string SCANBD_ACTION=email to signal trigger
scanbd: now sending signal trigger
scanbd: now flushing the dbus
scanbd: unref the signal
scanbd: using relative script path: scan.script, expanded to:
/usr/local/etc/scanbd/scan.script
scanbd: waiting for child: /usr/local/etc/scanbd/scan.script
scanbd: exec for /usr/local/etc/scanbd/scan.script
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
Re: [sane-devel] Raspbian Jessie - scanbd scripting issue
Wilhelm, thank you for taking the time to look into these issues. Following your advise I had a look into the source code and tried to understand, what happens in case, when e.g. button 3 is pressed and compared the logs with the information by pressing e.g. button 4 (log file excerpt - see below). The last common action for both button events is this logging information:respectiveThe message has been generated in file scanbuttond_wrapper.c in line 519 (source version 1.4.2).Next follows this if statement:Within the if statement the next logging message is generated and a new thread, where further action for script execution seems to be taken. The logging information is only printed for button 3! Obviously the if condition is false for button 4. I will try to debug this (I have no experience with debugging multi-threaded code), hoping to get closer to the problem, why no script is executed for button 1 and 4 - or do you already have an idea, what might be wrong? Kind regards, Rainer. syslog excerpt button 4 pressed button 3 pressed -- View this message in context: http://sane.10972.n7.nabble.com/Raspbian-Jessie-scanbd-scripting-issue-tp19611p19620.html Sent from the SANE - Dev mailing list archive at Nabble.com.-- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] UsbSnoop for Canon DR-C225
The log looks very similar to the DR-C125. Can you try building a current sane-backends git snapshot, and try the code? You might have to run as root user until we get the permissions sorted out. allan On Tue, Mar 31, 2015 at 9:31 AM, Nicolas Marchildon nico...@marchildon.net wrote: After few attempts (reboot, locked device, etc.), I managed to sniff only the device. The device is connected to the VirtualBox instance. https://drive.google.com/file/d/0B1s3C34oDHi5QTFyMDdmVVNaNTA/view Le mar. 31 mars 2015 à 07:20, m. allan noah kitno...@gmail.com a écrit : my scripts currently don't handle having this kind of mixed data in one log. I could update them I suppose, but it would be easier to get a smaller log- can you try bypassing the hub when making the log? Connect the scanner directly to the machine? allan On Mon, Mar 30, 2015 at 10:06 PM, Nicolas Marchildon nico...@marchildon.net wrote: This is on Windows XP. For some reason, I was not capturing anything until I included the USB hub *and* the scanner. Is the log worthless? Le lun. 30 mars 2015 à 21:33, m. allan noah kitno...@gmail.com a écrit : Your log has the packets from two different devices in it, or something else strange is going on. What OS was this captured on? allan On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah kitno...@gmail.com wrote: have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Raspbian Jessie - scanbd scripting issue
Wilhelm, I wasn't sure what you meant with Wilhelm Meier-2 wrote So please change the bool-expression in this if() to trueand test, please. So I commented the outer if statementand recompiled. That's working now for all buttons. Thanks a lot for your efforts! Kind regards, Rainer -- View this message in context: http://sane.10972.n7.nabble.com/Raspbian-Jessie-scanbd-scripting-issue-tp19611p19625.html Sent from the SANE - Dev mailing list archive at Nabble.com.-- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] UsbSnoop for Canon DR-C225
After few attempts (reboot, locked device, etc.), I managed to sniff only the device. The device is connected to the VirtualBox instance. https://drive.google.com/file/d/0B1s3C34oDHi5QTFyMDdmVVNaNTA/view Le mar. 31 mars 2015 à 07:20, m. allan noah kitno...@gmail.com a écrit : my scripts currently don't handle having this kind of mixed data in one log. I could update them I suppose, but it would be easier to get a smaller log- can you try bypassing the hub when making the log? Connect the scanner directly to the machine? allan On Mon, Mar 30, 2015 at 10:06 PM, Nicolas Marchildon nico...@marchildon.net wrote: This is on Windows XP. For some reason, I was not capturing anything until I included the USB hub *and* the scanner. Is the log worthless? Le lun. 30 mars 2015 à 21:33, m. allan noah kitno...@gmail.com a écrit : Your log has the packets from two different devices in it, or something else strange is going on. What OS was this captured on? allan On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah kitno...@gmail.com wrote: have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Raspbian Jessie - scanbd scripting issue
this line is printed in the logging data. The backend seems to work properly as well. Its just a guess: either there is no value change for button 1 and 4 or the values are not numerical. (?) I assume the hardware is ok as well, because I used the old scanbuttend with Debian Wheezy so far, and there scripts were executed for all buttons. Anyway - thank you for your support. I think there will be no other way to understand what's going on unless I've debugged the application. -- View this message in context: http://sane.10972.n7.nabble.com/Raspbian-Jessie-scanbd-scripting-issue-tp19611p19622.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] UsbSnoop for Canon DR-C225
$ /usr/local/bin/scanimage --version scanimage (sane-backends) 1.0.25git; backend version 1.0.25 $ sudo /usr/local/bin/scanimage -L device `canon_dr:libusb:002:011' is a CANON DR-C225 scanner $ sudo /usr/local/bin/scanimage --format=tiff image.tiff *** glibc detected *** /usr/local/bin/scanimage: double free or corruption (!prev): 0x01ef66c0 *** === Backtrace: = /lib64/libc.so.6[0x30dd875e66] /lib64/libc.so.6[0x30dd8789b3] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x10256)[0x7fb49804d256] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x114e7)[0x7fb49804e4e7] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x11d7e)[0x7fb49804ed7e] /usr/local/lib/sane/libsane-canon_dr.so.1(sane_canon_dr_start+0x7f1)[0x7fb498056651] /usr/local/bin/scanimage[0x404119] /lib64/libc.so.6(__libc_start_main+0xfd)[0x30dd81ed5d] /usr/local/bin/scanimage[0x401749] === Memory map: 0040-0040a000 r-xp fd:00 1070393 /usr/local/bin/scanimage 0060a000-0060b000 rw-p a000 fd:00 1070393 /usr/local/bin/scanimage 01e77000-01f2b000 rw-p 00:00 0 [heap] 30dd40-30dd42 r-xp fd:00 1470123 /lib64/ld-2.12.so 30dd61f000-30dd62 r--p 0001f000 fd:00 1470123 /lib64/ld-2.12.so 30dd62-30dd621000 rw-p 0002 fd:00 1470123 /lib64/ld-2.12.so 30dd621000-30dd622000 rw-p 00:00 0 30dd80-30dd98a000 r-xp fd:00 1470128 /lib64/libc-2.12.so 30dd98a000-30ddb8a000 ---p 0018a000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8a000-30ddb8e000 r--p 0018a000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8e000-30ddb8f000 rw-p 0018e000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8f000-30ddb94000 rw-p 00:00 0 30ddc0-30ddc83000 r-xp fd:00 1470129 /lib64/libm-2.12.so 30ddc83000-30dde82000 ---p 00083000 fd:00 1470129 /lib64/libm-2.12.so 30dde82000-30dde83000 r--p 00082000 fd:00 1470129 /lib64/libm-2.12.so 30dde83000-30dde84000 rw-p 00083000 fd:00 1470129 /lib64/libm-2.12.so 30de00-30de017000 r-xp fd:00 1470133 /lib64/libpthread-2.12.so 30de017000-30de217000 ---p 00017000 fd:00 1470133 /lib64/libpthread-2.12.so 30de217000-30de218000 r--p 00017000 fd:00 1470133 /lib64/libpthread-2.12.so 30de218000-30de219000 rw-p 00018000 fd:00 1470133 /lib64/libpthread-2.12.so 30de219000-30de21d000 rw-p 00:00 0 30de40-30de402000 r-xp fd:00 1470135 /lib64/libdl-2.12.so 30de402000-30de602000 ---p 2000 fd:00 1470135 /lib64/libdl-2.12.so 30de602000-30de603000 r--p 2000 fd:00 1470135 /lib64/libdl-2.12.so 30de603000-30de604000 rw-p 3000 fd:00 1470135 /lib64/libdl-2.12.so 30e780-30e7816000 r-xp fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30e7816000-30e7a15000 ---p 00016000 fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30e7a15000-30e7a16000 rw-p 00015000 fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30ec40-30ec407000 r-xp fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ec407000-30ec606000 ---p 7000 fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ec606000-30ec608000 rw-p 6000 fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ee00-30ee03f000 r-xp fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee03f000-30ee23f000 ---p 0003f000 fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee23f000-30ee24 rw-p 0003f000 fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee24-30ee25 rw-p 00:00 0 7fb496953000-7fb49696 r-xp fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb49696-7fb496b6 ---p d000 fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb496b6-7fb496b61000 rw-p d000 fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb496b61000-7fb496b6e000 r-xp fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496b6e000-7fb496d6d000 ---p d000 fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496d6d000-7fb496d6e000 rw-p c000 fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496d6e000-7fb496d7d000 r-xp fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496d7d000-7fb496f7d000 ---p f000 fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496f7d000-7fb496f7e000 rw-p f000 fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496f7e000-7fb496f8e000 r-xp fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb496f8e000-7fb49718d000 ---p 0001 fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb49718d000-7fb49718e000 rw-p f000 fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb49718e000-7fb4971b8000 r-xp fd:00 1207598 /usr/local/lib/sane/libsane-avision.so.1.0.25 7fb4971b8000-7fb4973b7000 ---p 0002a000 fd:00 1207598 /usr/local/lib/sane/libsane-avision.so.1.0.25 7fb4973b7000-7fb4973ba000 rw-p 00029000 fd:00 1207598 /usr/local/lib/sane/libsane-avision.so.1.0.25 7fb4973ba000-7fb4973bc000 rw-p 00:00 0 7fb4973bc000-7fb4973cf000 r-xp fd:00 1207586
Re: [sane-devel] UsbSnoop for Canon DR-C225
How about this: SANE_DEBUG_CANON_DR=25 scanimage --resolution 150 foo.pnm 2 drc225.log and send that log file. allan On Tue, Mar 31, 2015 at 5:33 PM, Nicolas Marchildon nico...@marchildon.net wrote: $ /usr/local/bin/scanimage --version scanimage (sane-backends) 1.0.25git; backend version 1.0.25 $ sudo /usr/local/bin/scanimage -L device `canon_dr:libusb:002:011' is a CANON DR-C225 scanner $ sudo /usr/local/bin/scanimage --format=tiff image.tiff *** glibc detected *** /usr/local/bin/scanimage: double free or corruption (!prev): 0x01ef66c0 *** === Backtrace: = /lib64/libc.so.6[0x30dd875e66] /lib64/libc.so.6[0x30dd8789b3] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x10256)[0x7fb49804d256] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x114e7)[0x7fb49804e4e7] /usr/local/lib/sane/libsane-canon_dr.so.1(+0x11d7e)[0x7fb49804ed7e] /usr/local/lib/sane/libsane-canon_dr.so.1(sane_canon_dr_start+0x7f1)[0x7fb498056651] /usr/local/bin/scanimage[0x404119] /lib64/libc.so.6(__libc_start_main+0xfd)[0x30dd81ed5d] /usr/local/bin/scanimage[0x401749] === Memory map: 0040-0040a000 r-xp fd:00 1070393 /usr/local/bin/scanimage 0060a000-0060b000 rw-p a000 fd:00 1070393 /usr/local/bin/scanimage 01e77000-01f2b000 rw-p 00:00 0 [heap] 30dd40-30dd42 r-xp fd:00 1470123 /lib64/ld-2.12.so 30dd61f000-30dd62 r--p 0001f000 fd:00 1470123 /lib64/ld-2.12.so 30dd62-30dd621000 rw-p 0002 fd:00 1470123 /lib64/ld-2.12.so 30dd621000-30dd622000 rw-p 00:00 0 30dd80-30dd98a000 r-xp fd:00 1470128 /lib64/libc-2.12.so 30dd98a000-30ddb8a000 ---p 0018a000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8a000-30ddb8e000 r--p 0018a000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8e000-30ddb8f000 rw-p 0018e000 fd:00 1470128 /lib64/libc-2.12.so 30ddb8f000-30ddb94000 rw-p 00:00 0 30ddc0-30ddc83000 r-xp fd:00 1470129 /lib64/libm-2.12.so 30ddc83000-30dde82000 ---p 00083000 fd:00 1470129 /lib64/libm-2.12.so 30dde82000-30dde83000 r--p 00082000 fd:00 1470129 /lib64/libm-2.12.so 30dde83000-30dde84000 rw-p 00083000 fd:00 1470129 /lib64/libm-2.12.so 30de00-30de017000 r-xp fd:00 1470133 /lib64/libpthread-2.12.so 30de017000-30de217000 ---p 00017000 fd:00 1470133 /lib64/libpthread-2.12.so 30de217000-30de218000 r--p 00017000 fd:00 1470133 /lib64/libpthread-2.12.so 30de218000-30de219000 rw-p 00018000 fd:00 1470133 /lib64/libpthread-2.12.so 30de219000-30de21d000 rw-p 00:00 0 30de40-30de402000 r-xp fd:00 1470135 /lib64/libdl-2.12.so 30de402000-30de602000 ---p 2000 fd:00 1470135 /lib64/libdl-2.12.so 30de602000-30de603000 r--p 2000 fd:00 1470135 /lib64/libdl-2.12.so 30de603000-30de604000 rw-p 3000 fd:00 1470135 /lib64/libdl-2.12.so 30e780-30e7816000 r-xp fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30e7816000-30e7a15000 ---p 00016000 fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30e7a15000-30e7a16000 rw-p 00015000 fd:00 1470132 /lib64/libgcc_s-4.4.7-20120601.so.1 30ec40-30ec407000 r-xp fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ec407000-30ec606000 ---p 7000 fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ec606000-30ec608000 rw-p 6000 fd:00 1072790 /usr/lib64/libusb-0.1.so.4.4.4 30ee00-30ee03f000 r-xp fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee03f000-30ee23f000 ---p 0003f000 fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee23f000-30ee24 rw-p 0003f000 fd:00 1081604 /usr/lib64/libjpeg.so.62.0.0 30ee24-30ee25 rw-p 00:00 0 7fb496953000-7fb49696 r-xp fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb49696-7fb496b6 ---p d000 fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb496b6-7fb496b61000 rw-p d000 fd:00 1207774 /usr/local/lib/sane/libsane-net.so.1.0.25 7fb496b61000-7fb496b6e000 r-xp fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496b6e000-7fb496d6d000 ---p d000 fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496d6d000-7fb496d6e000 rw-p c000 fd:00 1207574 /usr/local/lib/sane/libsane-abaton.so.1.0.25 7fb496d6e000-7fb496d7d000 r-xp fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496d7d000-7fb496f7d000 ---p f000 fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496f7d000-7fb496f7e000 rw-p f000 fd:00 1207578 /usr/local/lib/sane/libsane-agfafocus.so.1.0.25 7fb496f7e000-7fb496f8e000 r-xp fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb496f8e000-7fb49718d000 ---p 0001 fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb49718d000-7fb49718e000 rw-p f000 fd:00 1207582 /usr/local/lib/sane/libsane-apple.so.1.0.25 7fb49718e000-7fb4971b8000 r-xp fd:00 1207598 /usr/local/lib/sane/libsane-avision.so.1.0.25 7fb4971b8000-7fb4973b7000 ---p 0002a000 fd:00
