>
> Ah right, I was thinking about other handles.
>
> It seems that I may have found one possible cause, which may also
> cause the hang because we do not see the EOF. We should close the
> inherited handle after CreateProcess. And we should not always set
> inherit to true (as you stated earlier)
hi,
On Thu, Dec 6, 2012 at 3:51 PM, Ángel González wrote:
> On 06/12/12 13:52, Pierre Joye wrote:
>> hi,
>>
>> On Thu, Dec 6, 2012 at 12:40 PM, Ángel González wrote:
>>> On 06/12/12 09:49, Pierre Joye wrote:
hi!
While looking at the bug #63073, I was wondering if we could simply d
On 06/12/12 13:52, Pierre Joye wrote:
> hi,
>
> On Thu, Dec 6, 2012 at 12:40 PM, Ángel González wrote:
>> On 06/12/12 09:49, Pierre Joye wrote:
>>> hi!
>>>
>>> While looking at the bug #63073, I was wondering if we could simply do
>>> not pass open handles to the newly created child process.
>> Lo
hi,
On Thu, Dec 6, 2012 at 12:40 PM, Ángel González wrote:
> On 06/12/12 09:49, Pierre Joye wrote:
>> hi!
>>
>> While looking at the bug #63073, I was wondering if we could simply do
>> not pass open handles to the newly created child process.
>
> Looking at proc_open, where there is an explicit
On 06/12/12 09:49, Pierre Joye wrote:
> hi!
>
> While looking at the bug #63073, I was wondering if we could simply do
> not pass open handles to the newly created child process.
Looking at proc_open, where there is an explicit CreateProcess (we seem
to be using the library popen for the exec()...
hi!
While looking at the bug #63073, I was wondering if we could simply do
not pass open handles to the newly created child process.
The main issue in this bug is the session related handles. They are
passed to the parent process, which hangs until their are closed. It
indeed does not happen (us
