|
| 1 | + |
| 2 | +1.0.2 |
| 3 | +----- |
| 4 | + |
| 5 | +David Paktor: |
| 6 | +The most prominent change is that the Tokenizer's Message |
| 7 | +format has been expanded to show the current Output Position |
| 8 | +and, if applicable, the position relative to the end of the |
| 9 | +most recent PCI Header (to keep in sync with Offset numbers |
| 10 | +displayed by the DeTokenizer.) |
| 11 | + |
| 12 | +The Symbol-Tracing feature has been changed and expanded: |
| 13 | +Its Messages are no longer Advisories, but a class of their |
| 14 | +own called Trace-Notes. When a Traced Symbol is created, the |
| 15 | +Trace-Note Message gives the new Symbol's assigned FCode Token |
| 16 | +(when applicable) in addition to the Data-Type and Scope of |
| 17 | +the definition. |
| 18 | + |
| 19 | +A Trace-Note Message is now also issued when a Traced Symbol |
| 20 | +is invoked. Symbol-Tracing is not fooled by aliases, and a |
| 21 | +failed attempt to create or invoke a Traced Symbol will also |
| 22 | +cause a Trace-Note Message to be displayed. |
| 23 | + |
| 24 | +These expansions are based on some questions asked by one of |
| 25 | +my colleagues while maintaining a very large and convoluted |
| 26 | +body of Legacy code -- questions like: "Where is such-and-so |
| 27 | +definition coming from?" "Which version of it is being used |
| 28 | +here?" "How can I find where exactly that is in the Binary?" |
| 29 | + |
| 30 | +Another change is based on the recent exchange of letters with |
| 31 | +Rolf Schroedter concerning the use of the emit-fcode command. |
| 32 | +In the previous version, arguments to the emit-fcode command |
| 33 | +were limited to the range of user-defined FCodes, i.e., 0x800 |
| 34 | +to 0xFFF. The new version permits numbers in the entire range |
| 35 | +of valid FCodes, 0x010 to 0xFFF, which includes the sub-ranges |
| 36 | +that are reserved for Vendor-Specific FCodes. |
| 37 | + |
0 commit comments