Closed kvark closed 7 months ago
Tried removing both features here - makes no difference, still crashes in the same place.
Based on feedback from "gabydd" in Zed Discord, this issue is likely caused by our erroneous build.rs
instructions:
println!("cargo:rustc-env=MACOSX_DEPLOYMENT_TARGET=10.15.7");
println!("cargo:rerun-if-env-changed=ZED_BUNDLE");
if std::env::var("ZED_BUNDLE").ok().as_deref() == Some("true") {
// Find WebRTC.framework in the Frameworks folder when running as part of an application bundle.
println!("cargo:rustc-link-arg=-Wl,-rpath,@executable_path/../Frameworks");
} else {
// Find WebRTC.framework as a sibling of the executable when running outside of an application bundle.
println!("cargo:rustc-link-arg=-Wl,-rpath,@executable_path");
}
// Weakly link ReplayKit to ensure Zed can be used on macOS 10.15+.
println!("cargo:rustc-link-arg=-Wl,-weak_framework,ReplayKit");
// Seems to be required to enable Swift concurrency
println!("cargo:rustc-link-arg=-Wl,-rpath,/usr/lib/swift");
// Register exported Objective-C selectors, protocols, etc
println!("cargo:rustc-link-arg=-Wl,-ObjC");
These aren't supposed to be on with Linux. Closing.
I'm porting Zed to Linux - https://github.com/zed-industries/zed/pull/7343 It's currently crashing on startup even before
main
is entered. Call stacks are corrupted until I build with "safestack" sanitizer, in which case it produces the following stack: openssl-crash2-stack.txtStrace shows the configuration file read as the last thing:
I believe the callstack is coming from curl, which is coming to Zed through this dependency:
Note: was first submitted to https://github.com/sfackler/rust-openssl/issues/2160