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. C / C++ / MFC
  4. ProcessShellCommand() gives unhandled exception in VS2005

ProcessShellCommand() gives unhandled exception in VS2005

Scheduled Pinned Locked Moved C / C++ / MFC
7 Posts 4 Posters 0 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.
  • S Offline
    S Offline
    Shaileshhex
    wrote on last edited by
    #1

    ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)

    _ K D 3 Replies Last reply
    0
    • S Shaileshhex

      ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)

      _ Offline
      _ Offline
      _AnsHUMAN_
      wrote on last edited by
      #2

      Probably you don't initialize the parameters being sent to this function. What happens when you debug ur code. Can you post some relevant code snippet. it shouldn't be the function that would be causing a crash.

      Somethings seem HARD to do, until we know how to do them. ;-)_AnShUmAn_

      1 Reply Last reply
      0
      • S Shaileshhex

        ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)

        K Offline
        K Offline
        KarstenK
        wrote on last edited by
        #3

        Check all needed and Zero all unneeded parameters. :-\

        Greetings from Germany

        1 Reply Last reply
        0
        • S Shaileshhex

          ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)

          D Offline
          D Offline
          David Crow
          wrote on last edited by
          #4

          How are you verifying this? Have you called ParseCommandLine on the CCommandLineInfo first?

          "Love people and use things, not love things and use people." - Unknown

          "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

          S 1 Reply Last reply
          0
          • D David Crow

            How are you verifying this? Have you called ParseCommandLine on the CCommandLineInfo first?

            "Love people and use things, not love things and use people." - Unknown

            "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

            S Offline
            S Offline
            Shaileshhex
            wrote on last edited by
            #5

            HI all , Well i definitely do a ParseCommandLine(cmdInfo); and later if (!ProcessShellCommand(cmdInfo)) return FALSE; cmdInfo members are as follows m_nShellCommand = FileNew m_bRunEmbedded = 0; m_bRunAutomated = 0; m_bShowSplash =1; Rest all string members of cmdInfo are empty Callstack at unhandled exception msvcr80.dll!_crt_debugger_hook(int _Reserved=2015552886)

            S D 2 Replies Last reply
            0
            • S Shaileshhex

              HI all , Well i definitely do a ParseCommandLine(cmdInfo); and later if (!ProcessShellCommand(cmdInfo)) return FALSE; cmdInfo members are as follows m_nShellCommand = FileNew m_bRunEmbedded = 0; m_bRunAutomated = 0; m_bShowSplash =1; Rest all string members of cmdInfo are empty Callstack at unhandled exception msvcr80.dll!_crt_debugger_hook(int _Reserved=2015552886)

              S Offline
              S Offline
              Shaileshhex
              wrote on last edited by
              #6

              THis problem happens for my VS2003 code after i port it to VS2005

              1 Reply Last reply
              0
              • S Shaileshhex

                HI all , Well i definitely do a ParseCommandLine(cmdInfo); and later if (!ProcessShellCommand(cmdInfo)) return FALSE; cmdInfo members are as follows m_nShellCommand = FileNew m_bRunEmbedded = 0; m_bRunAutomated = 0; m_bShowSplash =1; Rest all string members of cmdInfo are empty Callstack at unhandled exception msvcr80.dll!_crt_debugger_hook(int _Reserved=2015552886)

                D Offline
                D Offline
                David Crow
                wrote on last edited by
                #7

                So how are you verifying that ProcessShellCommand() is the culprit?

                "Love people and use things, not love things and use people." - Unknown

                "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

                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