We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I originally raised this bug with libgit2 directly but response was that this is in fact a libgit2sharp error. libgit2/libgit2#5363
Use Repository.RetrieveStatus from libgit2sharp from inside Unity3D editor script.
No crash, instead returns RepositoryStatus
git2-106a5f2.dll caused an Access Violation (0xc0000005) in module git2-106a5f2.dll at 0033:7cb4ae65. Stack Trace of Crashed Thread 9380: 0x00007FFC7CB4AE65 (git2-106a5f2) git_diff_tree_to_index 0x00007FFC7CBB4B09 (git2-106a5f2) git_status_list_new 0x0000028C392EADBF (LibGit2Sharp) LibGit2Sharp.Core.NativeMethods.git_status_list_new() 0x0000028C392EAB9B (LibGit2Sharp) LibGit2Sharp.Core.Proxy.git_status_list_new() 0x0000028C392E57FB (LibGit2Sharp) LibGit2Sharp.RepositoryStatus..ctor() 0x0000028C392E49FB (LibGit2Sharp) LibGit2Sharp.Repository.RetrieveStatus()
git2-106a5f2, but also happens with e.g. git2-7ce88e6 (happened with all versions I tried).
Windows 10
The text was updated successfully, but these errors were encountered:
I'm having the same issue
Sorry, something went wrong.
No branches or pull requests
I originally raised this bug with libgit2 directly but response was that this is in fact a libgit2sharp error.
libgit2/libgit2#5363
Reproduction steps
Use Repository.RetrieveStatus from libgit2sharp from inside Unity3D editor script.
Expected behavior
No crash, instead returns RepositoryStatus
Actual behavior
Version of LibGit2Sharp (release number or SHA1)
git2-106a5f2, but also happens with e.g. git2-7ce88e6 (happened with all versions I tried).
Operating system(s) tested; .NET runtime tested
Windows 10
The text was updated successfully, but these errors were encountered: