SteveKing wrote:
> But *how* does it fail? Error message? Crash?
Takes up 18M of memory, and is entirely idle. Nothing on stdout, nothing
on stderr, no GUI alert whatsoever.
You can start several instances, none having any apparent effect (except
for memory consumption). Had the host app freeze a few times too, but of
course that needs not necessarily be tortoiseproc's fault.
The really strange thing is, however, that if I call the shell which
itself calls tortoiseproc, it works fine. Also, every normal console
command (like dir or svn) work just normal. You would exepect that
either none works or all, wouldn't you?
>> while(runLock) // this is not nice, but we want all operations
finished
>> ::wxYield();
> You're absolutely right, this is *not* nice. Please use
WaitForSingleObject...
WaitForSingleObject is Windows-specific of course, which is why I did
not use it. However, you made me realize I did not know about
wxCondition at all - which does just what I want, only with a mutex. So
if nothing else, that's an improvement already :-)
>
https://svn.collab.net/repos/tortoisesvn/trunk/src/TortoiseShell/ContextMenu.cpp
Thanks for the reference, CreateProcess won't do me, though. In that
case, I'd have to rewrite a lot of stuff and I shun being
Windows-dependent, too. Still, I'll have a look at the wxExec source on
next occasion to see what actually happens there.
If nothing helps, I'll leave it as it is, calling "cmd /C
tortoiseproc.exe" instead.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jun 21 20:57:07 2005