Feature request: Linux ELF files have a GNU extension that allows storing the debugging symbol table for an executable in an external file. There are two ways to reference this external file in an ELF file, but it appears as though the Intel debugger doesn't support automatically (or manually, for that matter) opening up an external symbol table when reading in an ELF executable. I've found this site useful for describing how both methods work:
http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html
Ideally, we would like to be able to use these methods in the debugger, since we like to keep our optimized executables high-speed and lightweight by stripping out the debugging symbols, but still allowing us to attach a debugger when things go awry. We have already confirmed that ifort supports passing in "-Wl,--build-id" to the linker, and things seem to work properly when we just use the "objcopy --only-keep-debug" and "objcopy -add-gny-debuglink" methods and debug using the "gdb" debugger (though the gdb debugger tends to crash quite a bit due to the alien variable types ifort creates).
Thanks
