Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Apr 2025 04:00:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 285734] graphics/epsonscan2: Illegal instruction core dump (14.2-RELEASE)
Message-ID:  <bug-285734-7788-xsjyXVWw7D@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-285734-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-285734-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285734

--- Comment #2 from David Horwitt <david@mhgeode.net> ---
Investigating further, the SIGILL was due to poorly handled NULL return val=
ues
from strtok() in Standalone/initdeviceselectcombobox.cpp and=20
Standalone/deviceselectorcombobox.cpp. It looks like the scanner returns it=
's
serial number in an unexpected format.

Fixing that, the program failed to communicate with the scanner, a Perfecti=
on
V500
(04b8:0130).

I convinced myself that the scanner requires es2intif (since epsonscan2.rul=
es
indicates
that PID 0130 requires the firmware file esfw7c.bin. I downloaded this firw=
ware
file,
installed it in compat/linux/usr/share/epsonscan2/ and modified=20
Scanner/Scanner.cpp to use es2intif as the interpreter. I could see that
es2intif was
being invoked, but epsonscan2 timed out trying to connect to the scanner (a=
nd
put the scanner in a state that required power cycling before repeating the
experiment).

es2intif is too opaque for me to pursue debugging; my conclusion is that th=
is
scanner is
not supported by epsonscan2 (or, at least not without someone with more
knowledge and=20
time than I working on it).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285734-7788-xsjyXVWw7D>