Re: seg-faults for network access

From: Henning Meier-Geinitz (
Date: Sun Dec 10 2000 - 02:34:10 PST

  • Next message: Oliver Rauch: "xsane-0.65 configure script"


    On Sat, Dec 09, 2000 at 09:36:18PM -0800, Daniel Kerry Hiltgen wrote:
    > #0 0x400d18a7 in memcpy (dstpp=0x805a890, srcpp=0x805a894, len=4294967292)
    > at ../sysdeps/generic/memcpy.c:55
    > #1 0x402ca03e in sanei_w_space (w=0x805a83c, howmuch=4) at sanei_wire.c:84
    > #2 0x402c9b78 in bin_w_word (w=0x805a83c, v=0xbffff780)
    > at sanei_codec_bin.c:94
    > #3 0x402ca248 in sanei_w_word (w=0x805a83c, v=0xbffff780) at sanei_wire.c:207


    4294967292 is the maximum (32 bit) unsigned int value minus 4. So
    maybe that's a signed/unsigned problem. If this was a byte order
    problem shouldn't the result be:

    0 0 0 4 is interpreted as 4 0 0 0 --> 67108864

    Similar things happen if scanning via saned on localhost (something
    like scanimage -d net:localhost:mustek:/dev/scanner). So I'm not sure
    if this is a byte order problem. Maybe Jochen can talk about this, he
    is looking for the local saned crashes. On the other hand there is a
    TODO list entry:

      * check net/saned
        - don't just ignore the byte-order for theimage data (needed to
          support depths > 8 bits/channel)

    > Any thoughts? Can I provide more information that might be helpful in
    > diagnosing the problem? (FWIW: Mustek 1200 LS)

    Oh! I'm very interested in this scanner. Is this a Legal size or A4
    scanner? Please send me the output (dbg.log) of the following

    SANE_DEBUG_MUSTEK=5 scanimage -L 2>dbg.log

    Is it working with the Mustek backend without problems?


    Source code, list archive, and docs:
    To unsubscribe: echo unsubscribe sane-devel | mail

    This archive was generated by hypermail 2b29 : Sun Dec 10 2000 - 02:37:39 PST