Run Disassembly Diagnoser without extra run

[adamsitnik]

• Implement reliable diagnoser synchronization
• Attach Dissasembly Diagnoser after we are done benchmarking

[adamsitnik]

I implemented the synchronization in very simple way.

Initially I was thinking about using some fancy stuff like Mutex. But Mutex throws NotSupportedException for .NET Core on MacOS and Linux. So it was not an option.

Then I realized that I can just write to std out and read std in in blocking way. It just works. So one process is writing signal and waiting for response by reading in blocking way from console.

This allowed to attach DissasemblyDiagnoser after benchmarks are done, without spawning new process. It also allows to get disassembly for Job.Dry (#542)

[AndreyAkinshin]

I like how it looks now!

[nietras]

@adamsitnik I have this issue in a benchmark I am doing (where I need IterationSetup and hence dry run), when will this be released?

[adamsitnik]

It's going to be part of the official 0.10.12 release, but we don't have any release date yet.

But it's available now on our CI feed:

<packageSources>
  <add key="bdn-nightly" value="https://ci.appveyor.com/nuget/benchmarkdotnet" />
</packageSources>

The latest package contains also parallel build, so overall performance should be improved.

[nietras]

@adamsitnik thanks that worked, however I am having issues with the disassembler. I've opened a separate issue for that #543