Creating symbols.o in tmpdir makes it hard to debug linker errors

It's impossible to rerun a failing linker command (as printed by cargo rustc -- --print link-args) because the symbols.o file is created in a tmpdir that is subsequently deleted.

Current output

... cc "-m64" "/tmp/xxx/symbols.o" ...

Desired output

symbols.o should be created under the target folder and not removed.

Rationale and extra context

I had to use inotifywait to copy the file before it was deleted for subsequent investigation of why the linker failed in a project with C++ dependencies so I could begin debugging why the linker command was failing.

Rust Version

rustc 1.89.0 (29483883e 2025-08-04)
binary: rustc
commit-hash: 29483883eed69d5fb4db01964cdf2af4d86e9cb2
commit-date: 2025-08-04
host: x86_64-unknown-linux-gnu
release: 1.89.0
LLVM version: 20.1.7

Anything else?

Also --print link-args is hard to discover since most search results point to -Z print-link-args which was removed after stabilisation almost 6 years ago.

No source file or test is named. Start by locating the compiler/linker path that creates symbols.o and handles --print link-args, then trace when its temporary directory is removed. Done means the object is placed under the target folder, retained, and usable when rerunning the printed linker command.