Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 44328 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
if I run a child process and grab the FileName for it, depending on _when_ I ask for the FileName, I am subject to get different results.
Here's a snapshot of a very basic repo where one can replicate the issue: https://gitlab.com/cdaringe/csharp-manage-child-process-demo/tree/8b605cef1d74fa38c04f7c6ea216f842848717de
- follow the readme instructions (very basic!)
- install the c# project's packages (just json.net)
- run the app. at this point https://gitlab.com/cdaringe/csharp-manage-child-process-demo/blob/8b605cef1d74fa38c04f7c6ea216f842848717de/ChildProcessHandles/Program.cs#L120 if you are running on OSX you will observe the that filename == '/usr/bin/env'.
- this is _not_ the binary that was called
- stop execution
- uncomment the following and rebuild: https://gitlab.com/cdaringe/csharp-manage-child-process-demo/blob/8b605cef1d74fa38c04f7c6ea216f842848717de/ChildProcessHandles/Program.cs#L77
- at the previous point of error, the filename is now correctly `/some/path/node`, per expectation
OS: mac osx 10.11
mono: Mono JIT compiler version 4.4.2 (mono-4.4.0-branch-c7sr1/f72fe45 Wed Jul 27 16:20:13 EDT 2016)
on windows, using .net proper, it also actually reports out cmd.exe in _both_ scenarios. not sure what to pick to reliably get the path to the running binary and the args it was provided, if they are even available. :/