Date: Fri, 30 Jun 2023 11:03:13 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 272291] devel/rust-analyzer: mark as LTO_UNSAFE Message-ID: <bug-272291-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272291 Bug ID: 272291 Summary: devel/rust-analyzer: mark as LTO_UNSAFE Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: rust@FreeBSD.org Reporter: tagattie@FreeBSD.org CC: rust@FreeBSD.org Flags: maintainer-feedback?(rust@FreeBSD.org) Assignee: rust@FreeBSD.org Attachment #243080 maintainer-approval?(rust@FreeBSD.org) Flags: CC: rust@FreeBSD.org Created attachment 243080 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D243080&action= =3Dedit Patch devel/rust-analyzer: mark as LTO_UNSAFE rust-analyzer won't run (repeatedly terminated with signal 6) when called f= rom VSCode's rust-analyzer extension. Error messages from rust-analyzer extension are as follows: [Info - 17:39:30] Connection to server got closed. Server will restart. [Info - 17:39:31] Connection to server got closed. Server will restart. [Info - 17:39:31] Connection to server got closed. Server will restart. [Info - 17:39:32] Connection to server got closed. Server will restart. [Error - 17:39:32] The Rust Analyzer Language Server server crashed 5 times= in the last 3 minutes. The server will not be restarted. See the output for mo= re information. Turning off LTO appears to work around the issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272291-7788>