in

Support Portal

Unable to debug applications linked with SD2.

Last post 11-13-2007 10:54 AM by Per Christian Moen. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 11-12-2007 3:11 PM

    Unable to debug applications linked with SD2.

    Loading of the SD2.dll file causes a breakpoint when the software is executed under a debugger. No further processing is possible. This happens using both the supplied C example and our own implementation. We are using Visual Studio 2005. Is there any compile time switches or similar that we should apply?

    Thanks

    Per Christian
     

    • Post Points: 4
  • 11-13-2007 9:05 AM In reply to

    • Ben Hejl
    • Top 10 Contributor
    • Joined on 05-11-2007
    • Cherry Hill, New Jersey
    • Code 39
    • Points 204

    Re: Unable to debug applications linked with SD2.

    The software protection for the SD2.dll does not allow the dll to load when a debugger is present.  We recommend if you need to run the program in the debugger to create a set of stub functions with the same signature as SwiftDecoder.  You can then control the behavior of the decoder when you are debugging your application.  When you need to test your program using SwiftDecoder, you can simply call the functions from the dll instead of the stub functions.

    Filed under: , ,
    • Post Points: 4
  • 11-13-2007 10:54 AM In reply to

    Re: Unable to debug applications linked with SD2.

    Not a very nice limitation or workaround. But I do understand your motivations.

    So far we have the following problems caused by your software protection:

    • Unable to debug applications linked with the SD2.dll.
    • Unable to run applications linked with the SD2.dll in a remote desktop session.
    • Unable to use the SD2.dll in a Java JNI library.

    We are implementing a barcode decode service to overcome these limitations. Communication with this server and the our other software is using shared memory. We are hoping that the cpu/memory overhead is not going to be to big.

    We are currently evaluating barcode software from three different suppliers. Your software is the only one that are giving us such problems. The others are the barcode decoding software from Matrox and Stemmer Imaging. These suppliers are also using USB dongles for software protection. The choice of software is going to be based on barcode decoding performance and cpu/memory consumption.

    • Post Points: 1
Page 1 of 1 (3 items)
Copyright Omniplanar, Inc. 2007
Powered by Community Server (Commercial Edition), by Telligent Systems