Re: Further 'debug details' of MAXISCAN A4 SCSI...

From: Henning Meier-Geinitz (hmg-ml@gmx.de)
Date: Sun Apr 08 2001 - 01:52:31 PDT

  • Next message: Henning Meier-Geinitz: "[dev] sane-config questions"

    Hi,

    I don't know anything about your scanner or the snapscan backend, but ...
    > /usr/lib/gimp/1.1/plug-ins/xscanimage (pid:505): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S
    > #0 0x401be198 in g_on_error_stack_trace () from /usr/lib/libglib-1.2.so.0
    > #1 0x401d54ec in g_thread_functions_for_glib_use ()
    > #2 0x62696c2f in ?? ()
     
    The question marks probably mean that some program/lib wasn't compiled
    with debug symbols so gdb can't get more information. I'm not sure if
    it's gtk or sane itsself. What you see is the error handling of glib
    so this doesn't help very much.

    You may try to enable debugging in SANE itsself to locate the bug.
    Something like:

    SANE_DEBUG_SANEI_SCSI=255 SANE_DEBUG_SNAPSCAN=255 gimp 2>debug.log

    Now try to scan. You should find the debug output in debug.log. Maybe
    someone can find the problem with this information.

    Bye,
      Henning 

    --
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

    This archive was generated by hypermail 2b29 : Sun Apr 08 2001 - 01:37:34 PDT