ProcessShellCommand() gives unhandled exception in VS2005
-
ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)
-
ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)
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_
-
ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)
-
ProcessShellCommand() call causes an unhandled exception in VS2005.. Anybody has solution plz reply.. THanks :-)
How are you verifying this? Have you called
ParseCommandLine
on theCCommandLineInfo
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
-
How are you verifying this? Have you called
ParseCommandLine
on theCCommandLineInfo
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
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)
-
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)
THis problem happens for my VS2003 code after i port it to VS2005
-
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)
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