Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues disassembling in "Run" mode #64

Open
kg opened this issue Sep 16, 2024 · 4 comments
Open

Issues disassembling in "Run" mode #64

kg opened this issue Sep 16, 2024 · 4 comments

Comments

@kg
Copy link

kg commented Sep 16, 2024

Frequently Disasmo fails to disassemble anything unless Run is checked. That's fine, it's not too hard to check Run.

Unfortunately Run frequently breaks at random in multiple ways:

  1. It will run a random other project in the solution instead of the one containing the method. If that project never terminates, disasmo hangs. For example my solution contains a BDN benchmark suite and then a simple test application that serves as a disassembly harness; disasmo will randomly choose to run the BDN suite and then hang. I have to unload the project and restart VS to fix this once it happens.

  2. Run will randomly fail sometimes with this error:

A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'E:\Documents\Projects\SimdDictionary\bin\Release\net8.0\Disasmo-v5.9.2\'.
Failed to run as a self-contained app.
  - The application was run as a self-contained app because 'E:\Documents\Projects\SimdDictionary\bin\Release\net8.0\Disasmo-v5.9.2\SimdDictionary.runtimeconfig.json' was not found.
  - If this should be a framework-dependent app, add the 'E:\Documents\Projects\SimdDictionary\bin\Release\net8.0\Disasmo-v5.9.2\SimdDictionary.runtimeconfig.json' file and specify the appropriate framework.

I have no idea how to work around the second one and I'm not sure why it only happens sometimes.

Thanks for this cool extension!

@kg
Copy link
Author

kg commented Sep 16, 2024

Looking closer, it seems like in 2. it's trying to run a class library instead of the active project that contains the method being disassembled (an exe).

@kg
Copy link
Author

kg commented Sep 16, 2024

Third failure mode if you unload a project and it tries to run that one anyway:

System.NotImplementedException: Not implemented (Exception from HRESULT: 0x80004001 (E_NOTIMPL))
   at EnvDTE.Project.get_FileName()
   at Disasmo.MainViewModel.<RunOperationAsync>d__80.MoveNext()

@EgorBo
Copy link
Owner

EgorBo commented Sep 17, 2024

Thanks! Let me take a look, I've seen some of these too

@kg
Copy link
Author

kg commented Sep 17, 2024

It seems like it may be determined by which project you have selected in Solution Explorer, like by clicking on it
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants