> ahh... correction... err... actually, builtin msvcrt _doesn't_ go
> according to plan!
>
> the data is returned (echo hello) but the python process hangs - it
> never sees the results come back.
correction: the reason for that was that my test case had "cmd /k
echo test" not "cmd /c echo test
On Thu, Jan 22, 2009 at 8:14 PM, Luke Kenneth Casson Leighton
wrote:
>>> So the problem lies elsewhere... do you have any more information on
>>> the debug output?
>>
>> hiya reece, thanks for responding. yes, i do - lemme get back to you
>> with it: i'm in the middle of a ... actually, i _do_ ha
>> So the problem lies elsewhere... do you have any more information on
>> the debug output?
>
> hiya reece, thanks for responding. yes, i do - lemme get back to you
> with it: i'm in the middle of a ... actually, i _do_ have it:
>
>
>
> it's a trace+all so is about 15mb (sorry!)
>
> i'm doing a r
On Thu, Jan 22, 2009 at 6:59 PM, Reece Dunn wrote:
> 2009/1/22 Luke Kenneth Casson Leighton :
>> 0010:trace:file:RtlGetFullPathName_U
>> (L"C:\\windows\\system32\\cmd.exe.manifest" 520 0xff9aaaf4 (nil))
>> attr= sharing=0001 disp=1 options=0
2009/1/22 Luke Kenneth Casson Leighton :
> 0010:trace:file:RtlGetFullPathName_U
> (L"C:\\windows\\system32\\cmd.exe.manifest" 520 0xff9aaaf4 (nil))
> attr= sharing=0001 disp=1 options=0010 ea=(nil).0x
> 0009:trace:seh:start_debugger Starting debugger
0010:trace:file:RtlGetFullPathName_U
(L"C:\\windows\\system32\\cmd.exe.manifest" 520 0xff9aaaf4 (nil))
attr= sharing=0001 disp=1 options=0010 ea=(nil).0x
0009:trace:seh:start_debugger Starting debugger "winedbg --auto 8 100"
?
ahh fer xxx
