I wouldn't call it an art form but to do systems you have to have a solid (and I mean SOLID) knowledge of the architecture. (I spend a lot of time in the principles of operations) and we debug at the bit level so we need to see all the instructions.
I like the 'not for the faint of heart' quip though. I'll tell my ulcer. ----- Original Message ---- From: David Boyes <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, April 2, 2008 10:37:23 AM Subject: Re: readelf/objdump displays > Still odd with all that Eclipse based stuff (which we use here...just > not me) that there is a need to analyze load modules. Over on the CICS > side, we pretty much can identify all we need to know about load modules > by version date and timestamp in the load modules. Yeah, but this is TPF. These guys care about instruction path lengths and a bunch of stuff that matters a lot in real-time programming, which is effectively what TPF is. You need to know where and how something got loaded, it's relationship to a bunch of system stuff, and how your transaction is interleaved with all the other stuff going on in the system at the same time. TPF programming is an art form, not a profession; not for the faint of heart. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
