-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
debug the AOT project ilc .sln went wrong #88459
Comments
You probably forgot to put |
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsDescriptionI build the AOT project from source
There is no problem but , i Set "ILCompiler" project in solution explorer as your startup project Set Application arguments in the project Debug options to the response file that was generated by regular native aot publishing of your test project e.g. Build & run using F5, It went wrong,The error is as follows: Please, how can I fix this error? The stack is as follows:
Reproduction StepsAs shown above Expected behaviorI want to debug the ilc .sln project Actual behaviorI want to debug the ilc .sln project, but it goes wrong Regression?No response Known WorkaroundsNo response Configuration
Other informationNo response
|
This issue has been marked |
Thank you very much, it is |
Description
I build the AOT project from source
There is no problem
but , i Set "ILCompiler" project in solution explorer as your startup project
Set Application arguments in the project Debug options to the response file that was generated by regular native aot publishing of your test project e.g.
G:\runtime8\artifacts\bin\repro\x64\Debug\compile-with-Debug-libs.rsp
Build & run using F5, It went wrong,The error is as follows:
Please, how can I fix this error?
The stack is as follows:
Reproduction Steps
As shown above
Expected behavior
I want to debug the ilc .sln project
Actual behavior
I want to debug the ilc .sln project, but it goes wrong
Regression?
No response
Known Workarounds
No response
Configuration
Other information
No response
The text was updated successfully, but these errors were encountered: