--- Comment #1 from Andrej Mitrovic <> 2011-10-16 
20:39:37 PDT ---
> I've also had this bug appear and disappear based on the current path of
> invocation of an executable, IOW sometimes an app would throw this exception 
> on
> exit if it was invoked on a directory UP from the current application
> directory, while in all other cases the exception would not be thrown.

When I say "an" executable I mean a much more complicated app than this small
test case.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to