Alistair Leslie-Hughes writes:
> Hi,
> Move DuplicateHandle to Create_Process.
> Added Makefile.in (missing from first patch)
>
> Changelog:
> mscoree: Implement ICorDebug CreateProcess
You should put everything in cordebug.c, there's no need to have a
separate file.
Alistair Leslie-Hughes writes:
> +{
> +HANDLE handle, thread;
> +DuplicateHandle(GetCurrentProcess(), lpProcessInformation->hProcess,
> +GetCurrentProcess(), &handle, 0, FALSE,
> DUPLICATE_SAME_ACCESS);
> +DuplicateHandle(GetCurrentProcess(), l
Hi Vincent,
On 5/11/2011 2:06 AM, Vincent Povirk wrote:
I'm curious why you've chosen to work on this. Is there a program
relying on this, or do you have some .NET debugging tools you'd like
to use? Or are you thinking we'd implement our own debugging tool as
well (perhaps extending winedbg)?
I'
I'm curious why you've chosen to work on this. Is there a program
relying on this, or do you have some .NET debugging tools you'd like
to use? Or are you thinking we'd implement our own debugging tool as
well (perhaps extending winedbg)?
Better debugging tools for wine/mono would definitely be nic
);
> +}
> memset( &si, 0, sizeof(STARTUPINFOW) );
> -ret = CreateProcessW( exe, arg, NULL, NULL, FALSE, 0, NULL, dir, &si,
> &info );
> +ret = CreateProcessW( NULL, cmd, NULL, NULL, FALSE, 0, NULL, dir, &si,
> &info );
You should still pass the exe name
Hi,
>+ sei.fMask = SEE_MASK_FLAG_DDEWAIT|
>+ SEE_MASK_FLAG_NO_UI|
>+ SEE_MASK_NO_CONSOLE|
>+ SEE_MASK_NOCLOSEPROCESS;
Console apps must be executed using exiting console, not a new one.
--
Kirill
Hello,
Is there a way to retrieve stdout and stderr when lauching unix program with
CreateProcess.
At this thime I can only get stdout / stderr from windows programs.
See You
Escuder Nicolas
On 7/9/07, Damjan Jovanovic <[EMAIL PROTECTED]> wrote:
This fixes an unusual bug where an older Winzip self-extracting
archive starts the executable just extracted in the wrong current
directory.
Changelog:
* CreateProcess should always specify the child's current directory.
Tes
Vitaliy Margolen <[EMAIL PROTECTED]> writes:
> Vitaliy Margolen wrote:
>> Removed todo from succeeding tests.
>>
>> Tests showed that only DACL can be set this way. Owner and group
>> are taken from the token. And we don't need SACL at this time if ever.
>> ---
>> dlls/advapi32/tests/security.c
Vitaliy Margolen wrote:
> Removed todo from succeeding tests.
>
> Tests showed that only DACL can be set this way. Owner and group
> are taken from the token. And we don't need SACL at this time if ever.
> ---
> dlls/advapi32/tests/security.c |3 ---
> dlls/kernel32/process.c| 12 ++
Robert Shearman wrote:
> Vitaliy Margolen wrote:
>> +
>> +/* set process security */
>> +if (ret && psa && psa->lpSecurityDescriptor)
>> +{
>> +NTSTATUS status;
>> +
>> +status = NtSetSecurityObject( info->hProcess,
>> DACL_SECURITY_INFORMATION,
>> +
Vitaliy Margolen wrote:
+
+/* set process security */
+if (ret && psa && psa->lpSecurityDescriptor)
+{
+NTSTATUS status;
+
+status = NtSetSecurityObject( info->hProcess,
DACL_SECURITY_INFORMATION,
+ psa->lpSecurityDescriptor );
+
Thomas Kho wrote:
It seems that it is not currently possible to get the exit code of a
unix program executed with _wspawnv(_P_WAIT, [unix app], [args])
because CreateProcess() does not return a handle to the new process.
_wspawnv() uses the handle to WaitForSingleObject() the end of
execution
It seems that it is not currently possible to get the exit code of a
unix program executed with _wspawnv(_P_WAIT, [unix app], [args])
because CreateProcess() does not return a handle to the new process.
_wspawnv() uses the handle to WaitForSingleObject() the end of
execution and also needs it to
> > According to MSDN documentation, CreateProcess
> > requires the app name(and the app name in the
> command
> > line) to be enclosed in quotes if it has spaces in
> it.
>
> Please check MSDN again. Here is what it says:
>
http://msdn.microsoft.com/library/defau
On Thu, 10 Nov 2005, Rufoo wrote:
I am looking at dlls/kernel/process.cc:get_file_name
that parses the command line. It seems to handle the
case where the application name has spaces in it but
the application name is not enclosed in double quotes.
According to MSDN documentation, CreateProcess
Rufoo wrote:
I am
looking for a test case for this, I am unable to find
it in kernel/tests/process.cc. Can someone clarify if
it is really required to handle this case?
How about writing a test case and show us that the behaviour is wrong?
Mike
I am looking at dlls/kernel/process.cc:get_file_name
that parses the command line. It seems to handle the
case where the application name has spaces in it but
the application name is not enclosed in double quotes.
According to MSDN documentation, CreateProcess
requires the app name(and the app
Saturday, September 10, 2005, 2:04:23 PM, Robert Shearman wrote:
> Vitaliy Margolen wrote:
>>Now I really need you help people.
>>
>>Ok, here is the problem:
>>LdrInitializeThunk is called from within start_process - the first thing to be
>>executed in the new process's context. But this is not rig
Vitaliy Margolen wrote:
Now I really need you help people.
Ok, here is the problem:
LdrInitializeThunk is called from within start_process - the first thing to be
executed in the new process's context. But this is not right. All what I found
so far indicates, that LdrInitializeThunk should be q
Now I really need you help people.
Ok, here is the problem:
LdrInitializeThunk is called from within start_process - the first thing to be
executed in the new process's context. But this is not right. All what I found
so far indicates, that LdrInitializeThunk should be queued as an APC, so it
exec
Today Raymond Chen posted an article about CreateProcess(), I haven't looked at our implementation
but if it works differently from his description someone may want to to fix it.
http://blogs.msdn.com/oldnewthing
Ivan.
Eric Pouech wrote:
As Mike reported, there was a bug in CreateProcess introduced with the
runtime info handling.
This patch should take care of it.
A+
Hi Eric,
This patch fixes the problem! thanks for your help!
Mike
23 matches
Mail list logo
