| 2 |
7u83 |
1 |
<!-- Crown Copyright (c) 1998 -->
|
|
|
2 |
<HTML>
|
|
|
3 |
<HEAD>
|
|
|
4 |
<TITLE>TDF Diagnostic Specification, Issue 3.0</TITLE>
|
|
|
5 |
</HEAD>
|
|
|
6 |
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#400080" ALINK="#FF0000">
|
|
|
7 |
<H1>TDF Diagnostic Specification, Issue 3.0</H1>
|
|
|
8 |
<H3>January 1998</H3>
|
|
|
9 |
<A HREF="diag4.html"><IMG SRC="../images/next.gif" ALT="next section"></A>
|
|
|
10 |
<IMG SRC="../images/no_prev.gif" ALT="previous section">
|
|
|
11 |
<IMG SRC="../images/no_top.gif" ALT="current document">
|
|
|
12 |
<A HREF="../index.html"><IMG SRC="../images/home.gif" ALT="TenDRA home page">
|
|
|
13 |
</A>
|
|
|
14 |
<IMG SRC="../images/no_index.gif" ALT="document index"><P>
|
|
|
15 |
<HR>
|
|
|
16 |
<DL>
|
|
|
17 |
<DT><A HREF="#intro"><B>1</B> - Introduction</A><DD>
|
|
|
18 |
<DT><A HREF="diag4.html"><B>2</B> - Diagnostic SORTs</A><DD>
|
|
|
19 |
<DT><A HREF="diag5.html"><B>3</B> - Reserved diagnostic TOKENs</A><DD>
|
|
|
20 |
<DT><A HREF="diag6.html"><B>4</B> - Proposed changes</A><DD>
|
|
|
21 |
</DL>
|
|
|
22 |
|
|
|
23 |
<HR>
|
|
|
24 |
|
|
|
25 |
<H1><A NAME="intro">1. Introduction</A></H1>
|
|
|
26 |
The TDF diagnostic information is intended to convey all that information,
|
|
|
27 |
used by current source level debuggers, which would conventionally
|
|
|
28 |
be part of an object file. Any particular installer will only use
|
|
|
29 |
those parts of this information which its native object format can
|
|
|
30 |
represent.
|
|
|
31 |
<P>
|
|
|
32 |
The version of the diagnostics described here is the first version.
|
|
|
33 |
It has only been tested with TDF produced from C programs. There are
|
|
|
34 |
known to be certain deficiencies relative to other languages (in particular
|
|
|
35 |
to FORTRAN). A later version will correct these deficiencies. The
|
|
|
36 |
changes already envisaged are detailed in <A HREF="diag6.html#0">section
|
|
|
37 |
4</A>, and would have minimal (if any) impact on C producers.
|
|
|
38 |
<P>
|
|
|
39 |
The diagnostic system introduces one new type of TDF linkable entities,
|
|
|
40 |
and currently adds two new units to the bitstream representation of
|
|
|
41 |
TDF.
|
|
|
42 |
<P>
|
|
|
43 |
Much of the actual annotation of procedure bodies is currently done
|
|
|
44 |
by reserved <CODE>TOKEN</CODE>s, which installers recognize specially.
|
|
|
45 |
These <CODE>TOKEN</CODE>s are described in <A HREF="diag5.html#0">section
|
|
|
46 |
3</A>.
|
|
|
47 |
<P>
|
|
|
48 |
There is a resemblance between the TDF diagnostic information and
|
|
|
49 |
Unix International's DWARF format. DWARF has similar aims to the TDF
|
|
|
50 |
diagnostics, and ensuring that complete DWARF information could be
|
|
|
51 |
generated provided a useful check during the development of the TDF
|
|
|
52 |
diagnostics. However the TDF diagnostics are intended to be architecture
|
|
|
53 |
(and format) neutral. No inference should be made about any link (present
|
|
|
54 |
or future) between DWARF and TDF diagnostics.
|
|
|
55 |
<P>
|
|
|
56 |
|
|
|
57 |
<HR>
|
|
|
58 |
<P><I>Part of the <A HREF="../index.html">TenDRA Web</A>.<BR>Crown
|
|
|
59 |
Copyright © 1998.</I></P>
|
|
|
60 |
</BODY>
|
|
|
61 |
</HTML>
|