当从非常简单的C#或C ++ gui程序执行时，PsExec挂起，该程序被编译为"Windows应用程序". [英] PsExec hang while being executed from a very simple c# or c++ gui program compiled as "windows application"
问题描述
从一个非常简单的C#或C ++ gui程序执行时，我正在经历PsExec挂起，这些程序被编译为"Windows应用程序"(而不是控制台应用程序").在下面 在下面的C)节中，我粘贴了代码以重现该问题，在下面的D)部分中，我粘贴了c ++代码以重现该问题.
I am experiencing PsExec hang while being executed from a very simple c# or c++ gui program compiled as "windows application" (not as "console application"). Under section C) below I have pasted the code to reproduce the problem and under section D) I have pasted the c++ code to reproduce the same problem.
当psexec挂起时，在本地附加到psexec之后的windbg输出将粘贴在B节下.
When the psexec hangs, the windbg output after being attached to psexec locally is pasted under section B).
我的程序在转储根据A)节粘贴的输出后挂起.
My program hangs after dumping the output pasted under section A).
如果将psexec命令替换为任何本地内容，例如，该程序将正常运行ProcessStartInfo("cmd.exe"，"/c目录c:\ windows \ *.*");
The program works fine if you replace psexec command with anything local e.g. ProcessStartInfo("cmd.exe", "/c dir c:\windows\*.*");
我想知道是否有人体验过并找到了解决方案.帮助将不胜感激.
I was wondering if anybody experienced it and found the solution for it. Help will be greatly appreciated.
谢谢， Sharrajesh
Thanks, Sharrajesh
A)psexec挂起时我的c#程序输出
A) My c# program output when psexec hang
PsExec v1.98-远程执行进程 版权所有(C)2001-2010 Mark Russinovich Sysinternals-www.sysinternals.com
PsExec v1.98 - Execute processes remotely Copyright (C) 2001-2010 Mark Russinovich Sysinternals - www.sysinternals.com
驱动器C中的卷没有标签.
Volume in drive C has no label.
B)挂起时psexec的Windbg输出
B) Windbg output for psexec while hang
3个Id:1614.15e4暂停:1个Teb:7efac000未冻结
ChildEBP RetAddr将Args转换为Child
02a3fe68 75a6d0c5 00000180 00000000 00000000 ntdll！NtReadFile + 0x15(FPO:[9,0,0])
02a3fecc 75cb18aa 00000180 02a3ff44 00010000 KERNELBASE！ReadFile + 0x118(FPO:[SEH])
02a3ff14 00403bde 00000180 02a3ff44 00010000 kernel32！ReadFileImplementation + 0xf0(FPO:[SEH])
警告:堆栈展开信息不可用.以下框架可能是错误的.
02a3ff2c 00000000 00291e48 00000000 02a5ff80 psexec + 0x3bde
3 Id: 1614.15e4 Suspend: 1 Teb: 7efac000 Unfrozen
ChildEBP RetAddr Args to Child
02a3fe68 75a6d0c5 00000180 00000000 00000000 ntdll!NtReadFile+0x15 (FPO: [9,0,0])
02a3fecc 75cb18aa 00000180 02a3ff44 00010000 KERNELBASE!ReadFile+0x118 (FPO: [SEH])
02a3ff14 00403bde 00000180 02a3ff44 00010000 kernel32!ReadFileImplementation+0xf0 (FPO: [SEH])
WARNING: Stack unwind information not available. Following frames may be wrong.
02a3ff2c 00000000 00291e48 00000000 02a5ff80 psexec+0x3bde
C)重现问题的c#代码
C) The c# code to reproduce the problem
using System;
using System.Windows.Forms;
using System.Diagnostics;
namespace WindowsFormsApplication1 {
static class Program {
static void DataReceiveHandler(object sender, DataReceivedEventArgs e) {
Debug.WriteLine(e.Data);
}
public static void NotWorkingPsExec() {
ProcessStartInfo startInfo = new ProcessStartInfo("psexec.exe",
"\\\\raj-2k3-32 cmd.exe /c dir c:\\windows\\*.*");
startInfo.UseShellExecute = false;
startInfo.CreateNoWindow = true;
startInfo.RedirectStandardOutput = true;
startInfo.RedirectStandardError = true;
Process proc = new Process();
proc.StartInfo = startInfo;
proc.ErrorDataReceived += new DataReceivedEventHandler(DataReceiveHandler);
proc.OutputDataReceived += new DataReceivedEventHandler(DataReceiveHandler);
proc.Start();
proc.BeginErrorReadLine();
proc.BeginOutputReadLine();
proc.WaitForExit();
Debug.WriteLine("Exit code = {0}", proc.ExitCode);
}
public static void WorkingPsExec() {
ProcessStartInfo startInfo = new ProcessStartInfo("psexec.exe",
"\\\\raj-2k3-32 cmd.exe /c dir c:\\windows\\*.*");
startInfo.UseShellExecute = false;
Process proc = new Process();
proc.StartInfo = startInfo;
proc.Start();
proc.WaitForExit();
Debug.WriteLine("Exit code = {0}", proc.ExitCode);
}
static void Main() {
NotWorkingPsExec();
//WorkingPsExec(); //If uncommented will work
}
}
}
D)重现问题的c ++代码
D) The c++ code to reproduce the problem
#include <windows.h>
#include <tchar.h>
#include <stdio.h>
#include <strsafe.h>
HANDLE g_hStdoutRd = NULL;
HANDLE g_hStdoutWr = NULL;
void StartCommand(TCHAR *szCmdline);
void ReadOutput();
void ErrorExit(PTSTR);
int APIENTRY _tWinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPTSTR lpCmdLine, int nCmdShow) {
SECURITY_ATTRIBUTES saAttr;
saAttr.nLength = sizeof(SECURITY_ATTRIBUTES);
saAttr.bInheritHandle = TRUE;
saAttr.lpSecurityDescriptor = NULL;
if (!CreatePipe(&g_hStdoutRd, &g_hStdoutWr, &saAttr, 0))
ErrorExit(TEXT("Stdout SetHandleInformation"));
if (!SetHandleInformation(g_hStdoutRd, HANDLE_FLAG_INHERIT, 0))
ErrorExit(TEXT("Stdout SetHandleInformation"));
TCHAR szCmdline[] = TEXT("psexec.exe \\\\raj-2k3-32 cmd.exe /c dir /s c:\\windows\\*.*"); // Not Working
//TCHAR szCmdline[] = TEXT("cmd.exe /c dir /s c:\\windows\\*.*"); // Working
StartCommand(szCmdline);
ReadOutput();
return 0;
}
void StartCommand(TCHAR *szCmdline) {
PROCESS_INFORMATION piProcInfo = {0};
STARTUPINFO siStartInfo = {0};
siStartInfo.cb = sizeof(STARTUPINFO);
siStartInfo.hStdError = g_hStdoutWr;
siStartInfo.hStdOutput = g_hStdoutWr;
siStartInfo.dwFlags |= STARTF_USESTDHANDLES;
BOOL bSuccess = CreateProcess(NULL, szCmdline, NULL, NULL, TRUE, 0, NULL, NULL, &siStartInfo, &piProcInfo);
if (!bSuccess)
ErrorExit(TEXT("CreateProcess"));
else {
CloseHandle(piProcInfo.hProcess);
CloseHandle(piProcInfo.hThread);
}
}
void ReadOutput() {
if (!CloseHandle(g_hStdoutWr))
ErrorExit(TEXT("StdOutWr CloseHandle"));
for (;; ) {
CHAR chBuf[4096] = {0};
DWORD dwRead;
BOOLEAN bSuccess = ReadFile(g_hStdoutRd, chBuf, ARRAYSIZE(chBuf), &dwRead, NULL);
if (!bSuccess || dwRead == 0)
break;
OutputDebugStringA(chBuf);
}
}
void ErrorExit(PTSTR lpszFunction) {
OutputDebugString(lpszFunction);
ExitProcess(1);
}
推荐答案
PSExec太随机地挂在我身上了.我没有按照您的方式重新创建问题，但是我使用了精神上看似值得继承的"PAExec"来避免麻烦: http://www.poweradmin.com/PAExec/
PSExec was hanging for me too randomly. I haven't put the effort into recreating the issue your way, but I have avoided my troubles by using "PAExec", a seemingly worthy successor in spirit: http://www.poweradmin.com/PAExec/
这篇关于当从非常简单的C#或C ++ gui程序执行时，PsExec挂起，该程序被编译为"Windows应用程序".的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
