[gs-bugs] [Bug 691995] New: Command line works, DLL does not

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Tue Feb 22 18:41:38 UTC 2011


           Summary: Command line works, DLL does not
           Product: Ghostscript
           Version: HEAD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P4
         Component: Client API
        AssignedTo: alex.cherepanov at artifex.com
        ReportedBy: marcos.woehrmann at artifex.com
         QAContact: gs-bugs at ghostscript.com
   Estimated Hours: 0.0
          Customer: 780

The customer reports that:

So here is what I am finding:  When I run gswin32.exe on this file it seems to
work.  When I load the gs32dll.dll and run directly from it (as we do in our
software) I get the following result in OUR output:

(M-D-Y)02-07-2011 14:03:44[PID:1024,TID:10]<->CVLtoPS:Executing 'gswin32.exe
-sstdout=nul-sDEVICE=tiffg4 -r204x196 -sOutputFile=C:\WINDOWS\TEMP\000000FA.TIF
C:\PROGRA~1\xxxxxx\outgoing\000000F9.000 '
(M-D-Y)02-07-2011 14:03:44[PID:870,TID:20090731]<->The detected revision info
is (870,20090731). Revision requested is (870,20090731)
(M-D-Y)02-07-2011 14:03:44[PID:0,TID:4241604]<!>LGSD:Processor exception
occured during PostScript initialization.  Process failed
(M-D-Y)02-07-2011 14:03:44[PID:1024,TID:998]<!>CVLtoPS:Return from execution
(0x3E6). Time for call = 0 secs

I compared the input file using beyond compare to see if we had changed the
input from the original and found that they are identical.

Any idea why running from the EXE vs the DLL would be any different?  I
actually tested from the same location with the EXE in the same folder as our
production gsdll32.dll file and got the same result.  It works from gswin32.exe
but not from the DLL.  Other (most) files work fine using the DLL only.

Any idea what could be going on?  Does error 0x3E6 ring a bell?

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list