> For one thing, I assumed that the section headers for a debug-only image > may be bogus garbage and not useful for some aspects of symbol > processing. I'm no longer sure that this is the case: if not, then we > don't need to bother with saving the section headers because once we > have chosen a reference image for the symbols, we know that image is > good enough for all the symbol processing. My previous assumption > that we may need to juggle parts of two ELF images in order to do the > symbol processing does complicate things -- hopefully we don't need it. The section headers in a .debug file are never "bogus garbage". Aside from sh_offset fields, they match the original unstripped file except that sh_type is changed to SHT_NOBITS for each section that is kept only in the stripped file. The one issue you have to deal with (in ET_DYN files) is that the addresses used in the section headers and everywhere else in the .debug file (symbol table st_value fields, all DWARF data containing addresses, etc.) may no longer match the addresses used in the stripped file, if prelink has changed that file after stripping. For this, all you need to do is calculate the offset between .debug file and stripped-file addresses. The way to do that is to examine the PT_LOAD program headers (just the first one is all you really need), and take the difference between the p_vaddr fields of the same PT_LOAD command in the two files. Thanks, Roland -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>