http://bugs.winehq.org/show_bug.cgi?id=11073
Jason Edmeades us@edmeades.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #37 from Jason Edmeades us@edmeades.me.uk 2012-11-19 15:23:34 CST --- I've just been reinvestigating this bug, which I could previously trivially reproduce earlier using the command logged in the +cmd attachment, as it overflowed some buffer somewhere... (cmd.exe /c "<very long lib statement with parms>"
I've just tried a few times to reproduce this without success so I believe one of the recent changes has fixed this. I changed the cmd.exe logic to handle the /C and /S options better, including its buffer management, and its likely I've 'accidentally' fixed this in a different way to the previous patch set.
Frederic - Are you still in a position to test this?
I'll close it as fixed, since I definitely could reproduce it and now I cant, but if you can reproduce it please attach another +cmd trace and I'll take a (quicker!) look.