`global_asm!` blocks have weird file/line mappings
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The report provides a reproducer in src/main.rs using core::arch::global_asm!, plus symbol and address lookup output from rust-objdump and addr2line. Start by reproducing the mismatch and inspecting the debug line information around asm_func at address 0x530. Done means stepping through asm_func reports its correct symbol and source location instead of unrelated libcore mappings.
由索引模型根据 Issue 内容生成。
描述
I tried this code:
cargo new --bin asm-sample
cd asm-sample
cargo add cortex-m-rt
cargo add semihosting --features=stdio
cat > src/main.rs << EOF
#![no_std]
#![no_main]
#[cortex_m_rt::entry]
fn main() -> ! {
semihosting::println!("Hello!");
asm_func();
semihosting::process::exit(0);
}
unsafe extern "C" {
safe fn asm_func();
}
core::arch::global_asm!(r#"
.text
.global asm_func
.type asm_func, %function
.p2align 2
asm_func:
.fnstart
.cfi_sections .debug_frame
.cfi_startproc
nop
nop
bx lr
.size asm_func, . - asm_func
.cfi_endproc
"#);
#[panic_handler]
fn panic_handler(info: &core::panic::PanicInfo) -> ! {
semihosting::println!("PANIC!: {}", info);
semihosting::process::exit(1);
}
EOF
cat > memory.x << EOF
MEMORY
{
FLASH : ORIGIN = 0x00000000, LENGTH = 4M
RAM : ORIGIN = 0x20000000, LENGTH = 4M
}
EOF
mkdir .cargo
cat > .cargo/config.toml << EOF
[build]
target = ["thumbv7em-none-eabihf"]
[target.thumbv7em-none-eabihf]
runner = [
"qemu-system-arm",
"-machine", "mps2-an386",
"-cpu", "cortex-m4",
"-semihosting",
"-display", "none",
"-kernel"
]
EOF
cat > build.rs << EOF
fn main() {
let out = &std::path::PathBuf::from(std::env::var_os("OUT_DIR").unwrap());
std::fs::write(out.join("memory.x"), include_bytes!("memory.x")).expect("Writing memory.x");
println!("cargo::rerun-if-changed=memory.x");
println!("cargo:rustc-link-arg=-Tlink.x");
println!("cargo:rustc-link-search={}", out.display());
}
EOF
cat > command.gdb << EOF
target remote :1234
break asm_func
layout split
continue
EOF
echo "In another window run 'rust-gdb -x command.gdb ./target/thumbv7em-none-eabihf/debug/asm-sample'"
cargo run -- -s -S
I expected to see this happen: stepping through asm_func shows the right symbol name and file/line info
Instead, this happened: I get shown random symbols from libcore, and lots of errors
warning: (Internal error: pc 0x400 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x400 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x400 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
(gdb) bt
#0 0x00000530 in core::num::imp::flt2dec::strategy::grisu::format_shortest_opt ()
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
#1 0x000005a8 in asm_sample::__cortex_m_rt_main () at src/main.rs:7
#2 0x000005de in asm_sample::__cortex_m_rt_main_trampoline () at src/main.rs:4
warning: (Internal error: pc 0x530 in read in CU, but not in symtab.)
Where did it get core::num::imp::flt2dec::strategy::grisu::format_shortest_opt from? I'm in asm_func.
I note the same issue comes from addr2line:
$ rust-objdump -t ./target/thumbv7em-none-eabihf/debug/asm-sample | grep asm_func
00000530 g F .text 00000006 asm_func
$ arm-none-eabi-addr2line -e ./target/thumbv7em-none-eabihf/debug/asm-sample 0x530
/rustc/58cf8f9c35b355199727627d07ae34a4e2846d67/library/core/src/num/imp/int_log10.rs:90
My Rust code at least appears to be mapped to the right file (and line 4 is right, but line 33 seems wrong):
$ rust-objdump -Ct ./target/thumbv7em-none-eabihf/debug/asm-sample | grep main
0000058e l F .text 00000048 asm_sample::__cortex_m_rt_main
000005d6 g F .text 00000008 main
$ arm-none-eabi-addr2line -e ./target/thumbv7em-none-eabihf/debug/asm-sample 0x583 0x5d6
/Users/jonathan/Documents/asm-bug/asm-sample/src/main.rs:33
/Users/jonathan/Documents/asm-bug/asm-sample/src/main.rs:4
Meta
rustc --version --verbose:
rustc --version -v
rustc 1.99.1 (58cf8f9c3 2026-10-13)
binary: rustc
commit-hash: 58cf8f9c35b355199727627d07ae34a4e2846d67
commit-date: 2026-10-13
host: aarch64-apple-darwin
release: 1.99.1
LLVM version: 23.1.1
- 主要语言
- Rust
- 星标
- 122k
- 派生
- 16.7k
- 平均合并
- 2 天 16 小时
- 30 天内合并 PR
- 515
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
rust-lang/rust 的其他 Issue
-
Remove unnecessary parentheses when suggesting to remove '&' from a pattern可能已有人在做 @BartSimpson001 于 1 天前认领。 未关闭A-diagnostics D-invalid-suggestion T-compiler
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
Windows `File::set_permissions` silently does nothing when clearing `readonly` leaves `FileAttributes == 0`可能已有人在做 @ChrisDenton 于 11 天前认领。 未关闭A-filesystem C-bug O-windows T-libs
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
A-run-make relnotes relnotes-needs-review relnotes-tracking-issue T-lang T-libs
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
A-LLVM O-Arm O-UEFI O-x86_64 relnotes relnotes-needs-review relnotes-tracking-issue T-compiler
难度 1/5 1 小时以内 新手友好度 72/100
rust-lang/rust#165504 · 1 条评论 ·
维护者通常 1 天内回复
-
relnotes relnotes-tracking-issue T-libs
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
bytecodealliance/wrpc#1785 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)未关闭
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
longbridge/nsh#2758 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
antithesishq/bombadil#473 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
libracoder/kiri#669 ·
维护者通常 1 天内回复