`global_asm!` blocks have weird file/line mappings

Aperta
#166,204 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
compilers

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

A-debuginfo A-global-asm A-LLVM C-bug T-compiler

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

Lingua principale
Rust
Stelle
122k
Fork
16.7k
Merge medio
2g 16h
PR unite (30g)
515

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rust-lang/rust

Tutte le issue di rust-lang/rust

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.