| PLEX86 | ||
|
Where should the type information be: in tags and descriptors 472
so one of the CP source enhancements indirectly arose from when i was originally doing cp67 pageable kernal code and trying to figure out the modified BPS loader problem ... I realized that when the BPS loader exited to the loaded program ... it pbutted the address of its symbol table (and the number of entries) in registers. so I did this hack that before CP wrote the kernel boot image to disk, it would copy the complete symbol table ... entry point symbols, entry point symbol type type (ESDID), and addresses ... to the end of the pageable kernel so it would be included in the boot image written to disk. this bit of cp67 code was never shipped to customers and in the morph from cp67 to vm370 pageable kernel support ... the part about appending the complete kernel symbol table was dropped. Statistical data about first years of usenet traffic Please pardon this intrusion. I've been ego-grepping on Google recently, mainly to see whether I'm remembered on... as part of DUMPRX kernel debugging enhancements, i included the kernel updates to automatically capture and include the complete kernel symbol table as part of the boot image. if DUMPRX found a complete symbol table ... it would optional display the appropriate addresses as "aboslute" ... or as relative to closest "type 0 kernel entry point symbol" plus displacement. this was an alternative to the "IPCS" supported option which allowed the appending of a kernel subset symbol table as part of post processing. One of the issues with doing it as part of post processing was that the selected subset table might be out-of-sync with the kernel actually being processed. having it appended as part of the base kernel image, made sure you were never dealing with an out-of-sync kernel symbol table. couple old posts describing compiler-buttembler generated ESD image format (i.e. the imput for loaded processing ... stuff that then went into the loader symbol table): -- Where should the type information be: in tags and descriptors 473 That was my point. The majority of the evolution has been the fact that one can put a system in one's home...
|
||||||||
Where should the type information be: in tags and descriptors 473 Alt Folklore Computers Newsgroups Where should the type information be: in tags and descriptors 471 |
||||||||