|
Are you sure there is no compression? It may be that DMPOBJ decompresses
the object for you.
We can not be sure unless we get the answer from one of the developers of
the OS. I'm fairly certain the source statements aren't compressed because the first column of the report appears to be an address value the increment of which ties in with the number of bytes being shown on each line (32 or x'20'). I wouldn't have expected the DMPOBJ to do any decompression, but I would have thought having the debugger perform decompression of source wouldn't have made a noticeable hit on performance. Jonathan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.