Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What library routines and header files have changed to support ELF?

0
Posted

What library routines and header files have changed to support ELF?

0

We changed the nlist() routine to handle 32-bit ELF, 64-bit ELF and a.out format files. It now uses file mapping to read symbol tables and string tables. Since there can be confusion about whether a symbol needs to be prepended with an underscore, nlist() checks for the requested symbol with or without its prepended underscore. The nlist structure itself did not change for ELF, although ELF’s symbols look nothing like nlist records. Since ELF programs put their user stack in a different location from a.out programs, we had to change the -lkvm library to look for each process’s stack at a location specific to that process, and to avoid making assumptions about the layout of the process. The headers and still describe a.out format files. The new header describes ELF format files. You may include both and in the same source file.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123