Hi.... On 9/22/09, Krzysztof Poc <[email protected]> wrote: > Hello > > I have 2 questions about core dumping. > > 1. I read in man core about dumping the following mappings: > bit 0 Dump anonymous private mappings. > bit 1 Dump anonymous shared mappings. > bit 2 Dump file-backed private mappings. > bit 3 Dump file-backed shared mappings. > > Could you assign each mapping to a ELF program section e.g. code, data, > stack, heap, bss etc.
anonymous private mappings to me could be initialized and unitialized data section, or specificly anything that is mmaped anonymously using MAP_PRIVATE flag. Most of these data section are not shared (precisely, COW-ed) after we do fork(). .code section, at least from what I see from strace (that means shared libs too) are mapped as private. So, to conclude, by doing strace when executing certain binaries (i did "strace ls") you can see that most likely they are all mapped privately. shared mapping is likely requested explicitly. > 2. Is there any tool that shows me what an individual mappings in a core > dump file are ? > e.g.: > start-address end-address type-of-mapping > 0x0 0x100 code try objdump -- regards, Mulyadi Santosa Freelance Linux trainer blog: the-hydra.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
