FS#73976 - [cargo-outdated] Rebuild to avoid segfault
Attached to Project:
Community Packages
Opened by Danilo (danilo) - Sunday, 27 February 2022, 18:09 GMT
Last edited by Orhun Parmaksız (orhun) - Saturday, 16 April 2022, 23:58 GMT
Opened by Danilo (danilo) - Sunday, 27 February 2022, 18:09 GMT
Last edited by Orhun Parmaksız (orhun) - Saturday, 16 April 2022, 23:58 GMT
|
Details
Description:
cargo-outdated currently segfaults when running in a project with git dependencies, if libgit2 1.4 is installed: https://github.com/kbknapp/cargo-outdated/issues/307 Top three lines in the coredump stacktrace: Stack trace of thread 12556: #0 0x00007f36bad7efc0 n/a (libgit2.so.1.4 + 0xa3fc0) #1 0x00007f36bad80aae git_remote_fetch (libgit2.so.1.4 + 0xa5aae) #2 0x0000557cd57eeb11 n/a (cargo-outdated + 0x24bb11) Solution: Rebuild the crate with latest dependencies. Additional info: * package version(s): cargo-outdated 0.10.2-4 and libgit2 1.4.2-1 Steps to reproduce: Run `cargo outdated` in a project with git dependencies. |
This task depends upon
Closed by Orhun Parmaksız (orhun)
Saturday, 16 April 2022, 23:58 GMT
Reason for closing: Fixed
Additional comments about closing: upstream released a new version with the fix (0.11.1-1)
Saturday, 16 April 2022, 23:58 GMT
Reason for closing: Fixed
Additional comments about closing: upstream released a new version with the fix (0.11.1-1)
This affects the 0.11 release as well. We'll have to wait for an upstream fix.
As you said, rebuilding won't help here. Other cargo-* plugins are potentially affected by this issue as well.