[Bug 37780] cmd does not wait for bash script completion

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=37780

Jason Edmeades <us at edmeades.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |us at edmeades.me.uk

--- Comment #2 from Jason Edmeades <us at edmeades.me.uk> ---
I'm working through the cmd bugs and came across this old one. I'm not really
sure how to solve this, so adding some notes here. You might want to read
bug#34730 as well where there was a long discussion on parts of this.

The problem is when you ask to run fred.exe, we look up the file fred.exe and
ask the operating system for some information about fred.exe... Specifically we
call SHGetFileInfo which should tell us whether the binary is a windows or
console program. It fails to recognize that fred.exe is a valid program and
returns 0, and as the low and high word is zero this means we dont bother
waiting for it, however we still ask for it to be run.

One initial thought was to set it to e.g. 1, so we did wait - Doing this made
no difference - a CreateProcess for a unix binary worked, but you do not get
back a valid handle you can wait on for when the process ends, so even though
the code tries to wait it fails.

I feel this ought to be closed dup of 34730, which is a wont fix but I will see
if I can put an email onto wine-devel for clarity

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.