<div dir="ltr"><div dir="ltr"><div>Hi,</div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 24, 2023 at 11:34 AM Atom Mac <<a href="mailto:atom.mac@gmail.com">atom.mac@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Setting the `SANE_DEBUG_PIXMA` env variable and running `scanimage` with<br>
all of the arguments included in my original post (ex. for the doc<br>
feeder, etc.) causes `scanimage` to immediately exit and print<br>
`Segmentation Fault`. This differs from when the env variable is unset,<br>
which seems to cause a delay before the seg fault occurs.<br>
<br>
I'm a noob when it comes to gdb but assuming I captured the stack trace<br>
correctly, what I'm seeing is:<br>
<br>
```<br>
(gdb) exec-file scanimage \<br>
--device=pixma:04A91787_77BF9D \<br>
--source="Automatic Document Feeder" \<br>
--batch=out%d.png \<br>
--format=png \<br>
--mode=Gray \<br>
-vvvvvv<br>
(gdb) run<br>
Starting program: /usr/local/bin/scanimage scanimage \<br>
--device=pixma:04A91787_77BF9D \<br>
--source="Automatic Document Feeder" \<br>
--batch=out%d.png \<br>
--format=png \<br>
--mode=Gray \<br>
-vvvvvv<br>
<br>
Program received signal SIGSEGV, Segmentation fault.<br>
0x76fa11fc in memchr () from /lib/ld-musl-armhf.so.1<br>
(gdb) bt<br>
#0 0x76fa11fc in memchr () from /lib/ld-musl-armhf.so.1<br>
#1 0x76fa2114 in strnlen () from /lib/ld-musl-armhf.so.1<br>
#2 0x76f6ae9c in ?? () from /lib/ld-musl-armhf.so.1<br>
Backtrace stopped: previous frame identical to this frame (corrupt stack?)<br>
````<br></blockquote><div><br></div><div><div dir="ltr"><div>Well that sounds a lot different from what I thought.</div><div>If I have time, I will try to install Alpine on a Pi that I have here and try it out with my MX492.</div><div>Can't make any promises though.....</div><div><br></div><div>Cheers,</div><div>Ralph<br></div></div> </div></div></div>