Alpine Linux causes a segmentation fault
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- linux, rust
调研方向
Reproduce the crash with cargo run --example networking on Alpine Linux and inspect src/lib.rs around load_xlib_with_error_hook at lines 169-171 and its initializer at line 196. Use the provided gdb backtrace to investigate the null error representation; done means the networking example no longer segfaults on Alpine.
由索引模型根据 Issue 内容生成。
描述
Seen in winit-block-on:
$ cargo run --example networking
Finished dev [unoptimized + debuginfo] target(s) in 0.08s
Running `target/debug/examples/networking`
[1] 17749 segmentation fault cargo run --example networking
gdb gives this backtrace:
(gdb) bt
#0 std::io::error::{impl#8}::fmt () at library/std/src/io/error.rs:951
#1 0x00007ffff7b16a1c in core::fmt::rt::Argument::fmt () at library/core/src/fmt/rt.rs:138
#2 core::fmt::write () at library/core/src/fmt/mod.rs:1094
#3 0x00007ffff7b0c054 in core::fmt::Write::write_fmt<alloc::string::String> ()
at library/core/src/fmt/mod.rs:192
#4 alloc::fmt::format::format_inner () at library/alloc/src/fmt.rs:610
#5 0x00007ffff76c6cb5 in alloc::fmt::format::{closure#0} ()
at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/fmt.rs:614
#6 0x00007ffff76c66de in core::option::Option<&str>::map_or_else<&str, alloc::string::String, alloc::fmt::format::{closure_env#0}, fn(&str) -> alloc::string::String> (self=...,
default=..., f=0x0)
at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/option.rs:1181
#7 0x00007ffff76c6c4f in alloc::fmt::format (args=...)
at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/fmt.rs:614
#8 0x00007ffff76c73bf in tiny_xlib::XLIB___rust_ctor___ctor::initer::load_xlib_with_error_hook::error<std::io::error::Error> (e=...) at src/lib.rs:169
#9 0x00007ffff76c5fd3 in core::ops::function::FnOnce::call_once<fn(std::io::error::Error) -> std::io::error::Error, (std::io::error::Error)> ()
at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/ops/function.rs:250
#10 0x00007ffff76c6a09 in core::result::Result<tiny_xlib::ffi::Xlib, std::io::error::Error>::map_err<tiny_xlib::ffi::Xlib, std::io::error::Error, std::io::error::Error, fn(std::io::error::Error) -> std::io::error::Error> (self=..., op=0x0)
at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/result.rs:829
#11 0x00007ffff76c71e1 in tiny_xlib::XLIB___rust_ctor___ctor::initer::load_xlib_with_error_hook () at src/lib.rs:171
#12 0x00007ffff70d9fbe in tiny_xlib::XLIB___rust_ctor___ctor::initer () at src/lib.rs:196
#13 0x00007ffff7af9555 in libc_start_init () at ../src_musl/src/env/__libc_start_main.c:64
#14 0x00007ffff7af957a in libc_start_main_stage2 ()
at ../src_musl/src/env/__libc_start_main.c:92
#15 0x00007ffff70da064 in _start ()
Setting a breakpoint inside of the error printer gives me this:
(gdb) print e
$1 = std::io::error::Error {repr: std::io::error::repr_bitpacked::Repr (core::ptr::non_null::NonNull<()> {pointer: 0x0}, core::marker::PhantomData<std::io::error::ErrorData<alloc::boxed::Box<std::io::error::Custom, alloc::alloc::Global>>>)}
So it's some kind of weird niche issue. My guess is that somehow the dynamically linked functions are null when Alpine links them together, thus causing Rust to assume that it's somehow gotten a null IO error.
- 主要语言
- Rust
- 星标
- 7
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
rust-windowing/tiny-xlib 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
rust-windowing/tiny-xlib#16 · 3 条评论 ·
-
难度 3/5 1-2 天 新手友好度 42/100
rust-windowing/tiny-xlib#15 ·
-
难度 4/5 3-5 天 新手友好度 30/100
rust-windowing/tiny-xlib#11 ·
-
Flaky CI Test未关闭
难度 4/5 3-5 天 新手友好度 25/100
查看 rust-windowing/tiny-xlib 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
aws-samples/sample-pacer#76 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
axodotdev/cargo-dist#2523 ·
维护者通常 2 天内回复