Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. COM
  4. Help with Unusal Debug Error.

Help with Unusal Debug Error.

Scheduled Pinned Locked Moved COM
helpcomdebuggingtutorialquestion
3 Posts 2 Posters 3 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    Joseph Dempsey
    wrote on last edited by
    #1

    I need some help. I am experiencing an error while attempting to use a function I have imported from a COM inproc DLL. After I import the library I start using it. There is one function that gives me a debug error. It comes out of the i386\chkesp.c file. It says that a ChkESP error has occurred and that it usually happens with an issue with using a function pointer that using a different calling convention that a defined function (I checked and this isn't it. My calling conventions are fine __stdcall). After tracing through the code I find out that it occurs after the COM function completes but before the next line of code exectued in the .tlh file's wrapper functions. Note that if I just click ignore the error everything still works fine. In my app I am using the library in the code looks something like: ITCPServerPtr tcp = ITCPServerPtr( CLSID_CoTCPPort ); tcp->OpenPort(); //works bool check = tcp->SetBuffers(newSize); //works bool check2 = tcp->StartupServer(port); ... the error happens after the actual COM StartupServer func. executes but before a return happens. Has anyone ever seen anything like this before. If so anyone know how to fix it? I am in the dark. FYI: When I build release ver. all works and no error pops up. Joseph Dempsey jdempsey@cox.rr.com Joseph.Dempsey@thermobio.com "Software Engineering is a race between the programmers, trying to make bigger and better fool-proof software, and the universe trying to make bigger fools. So far the Universe in winning." --anonymous

    C 1 Reply Last reply
    0
    • J Joseph Dempsey

      I need some help. I am experiencing an error while attempting to use a function I have imported from a COM inproc DLL. After I import the library I start using it. There is one function that gives me a debug error. It comes out of the i386\chkesp.c file. It says that a ChkESP error has occurred and that it usually happens with an issue with using a function pointer that using a different calling convention that a defined function (I checked and this isn't it. My calling conventions are fine __stdcall). After tracing through the code I find out that it occurs after the COM function completes but before the next line of code exectued in the .tlh file's wrapper functions. Note that if I just click ignore the error everything still works fine. In my app I am using the library in the code looks something like: ITCPServerPtr tcp = ITCPServerPtr( CLSID_CoTCPPort ); tcp->OpenPort(); //works bool check = tcp->SetBuffers(newSize); //works bool check2 = tcp->StartupServer(port); ... the error happens after the actual COM StartupServer func. executes but before a return happens. Has anyone ever seen anything like this before. If so anyone know how to fix it? I am in the dark. FYI: When I build release ver. all works and no error pops up. Joseph Dempsey jdempsey@cox.rr.com Joseph.Dempsey@thermobio.com "Software Engineering is a race between the programmers, trying to make bigger and better fool-proof software, and the universe trying to make bigger fools. So far the Universe in winning." --anonymous

      C Offline
      C Offline
      Chris Losinger
      wrote on last edited by
      #2

      i get this when the IDL and the DLL disagree on something. usually a rebuild-all fixes it for me. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com

      J 1 Reply Last reply
      0
      • C Chris Losinger

        i get this when the IDL and the DLL disagree on something. usually a rebuild-all fixes it for me. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com

        J Offline
        J Offline
        Joseph Dempsey
        wrote on last edited by
        #3

        tried that already.. Doesn't do any good. Thanks though. Joseph Dempsey jdempsey@cox.rr.com Joseph.Dempsey@thermobio.com "Software Engineering is a race between the programmers, trying to make bigger and better fool-proof software, and the universe trying to make bigger fools. So far the Universe in winning." --anonymous

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups