Linking to static native libraries loses the native library debug info

[brson]

I've noticed that when I link static native libraries to Rust crates we lose the debug info from the native libraries. I assume that there is some minimum we can do to signal to the linker that we really want to keep that information.

[graydon]

non-critical for 0.6, de-milestoning

[graydon]

Reproduced, but I have no idea why it's happening; if I copy the -Z print-link-args arguments and feed them to gcc by hand, this doesn't happen.

Nominating for production ready.

[graydon]

accepted for production-ready milestone

[emberian]

cc @michaelwoerister

[pnkfelix]

Assigning P-low.

[emberian]

cc @luqmana want to take a look at this?

[michaelwoerister]

Cannot reproduce this anymore. My example program:

#[link(name = "somelib", kind = "static")]
extern {
    fn some_c_function();
}

fn main() {
    unsafe {
        some_c_function();
    }
}

I had no problem stepping into the C function some_c_function compiled with gcc. I don't think this issue exists anymore.