Loading ...
Sorry, an error occurred while loading the content.

946RE: [cc2-dev-l] It's beautiful... except for the part where it doesn't work

Expand Messages
  • Peter Olsson
    Apr 5, 2012
    • 0 Attachment

      Are you able to use the built in debugger in Visual Studio?

       

      1.     Set the output to the CC3-folder.

      2.     Press F9 on the line you want to break

      3.     Press F5 to run in the debugger and select FCW32.exe as your target.

       

      Peter

       

       

      From: cc2-dev-l@yahoogroups.com [mailto:cc2-dev-l@yahoogroups.com] On Behalf Of BC Holmes
      Sent: Thursday, April 05, 2012 3:36 AM
      To: cc2-dev-l@yahoogroups.com
      Subject: [cc2-dev-l] It's beautiful... except for the part where it doesn't work

       

       


      Sigh.

      I feel like I'm in the home stretch. I've got the majority of my code
      ported, and it runs in stand-alone mode. I've got an interface to my
      code that works with the XP API and with a simple file interface. I've
      got all my code loaded up into Visual Studio, and all the compile
      problems have been figured out.

      But the code doesn't work when I invoke it from CC3. Specifically, I
      get the hourglass and my CC3 process starts consuming a lot of memory.
      Never a good sign with a Windows/C++ program.

      I'm sure there's some dumb little thing that's a problem for me. But
      what techniques do people use to debug XPs running in CC3? Is there any
      kind of existing logging API? Or sumpthing like that?

      BCing you
      --
      B.C. Holmes \u2625 http://www.bcholmes.org/
      "All my life I've wanted to be somebody; I guess I should've been
      more specific." -- Lily Tomlin

    • Show all 7 messages in this topic