[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: binfmt_elf.o as loadable module in 2.4.20
Hi..
> cat /proc/ksyms on my running system which has built in binfmt_elf.o,
> doesn't show symbols related to binfmt_elf.o but still it generates
> application coredump upon seg-fault.
I think that's because the related symbol is stripped or isn't there
because it's inlined/static
> I added some printks, compiled binfmt_elf.o and inserted in running
> kernel. After inserting the module, i can see the symbols in cat
> /proc/ksyms. Now when i generated application seg-fault, core dump
> was generated as before but I could find my printks in
> /var/log/messages. which indicates, that the code is flowing from
> there.
Ehm, I think, that's because the kernel simply reassign elf struct to
the new inserted structure via the loadable module. In other word, all
the ELF operations now refers to your newly inserted, not on the old
adddresses anymore
> The question is if the code is flowing from binfmt_elf.o, how
> coredump was getting generated before i inserted it.
Are you sure? You said you have made it as built in, right?
> 3. In 2.6 kernel configuration, the same cannot be compiled as
> module. Can any one tell me the reason behind this?
I think the rationale is: everyone almost 99.99% needs ELF when running
Linux. The rest 0.01% is maybe for someone who completely use another
binary format.
regards,
Mulyadi
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/