up | Inhaltsverzeichniss | Kommentar

Manual page for ADBGEN(8)

adbgen - generate adb script


/usr/lib/adb/adbgen filename.adb ...


adbgen makes it possible to write adb.1 scripts that do not contain hard-coded dependencies on structure member offsets. The input to adbgen is a file named filename.adb which contains adbgen header information, then a null line, then the name of a structure, and finally an adb script. adbgen only deals with one structure per file; all member names are assumed to be in this structure. The output of adbgen is an adb script in filename. adbgen operates by generating a C program which determines structure member offsets and sizes, which in turn generates the adb script.

The header lines, up to the null line, are copied verbatim into the generated C program. Typically these include C #include statements to include the header files containing the relevant structure declarations.

The adb script part may contain any valid adb commands (see adb.1 and may also contain adbgen requests, each enclosed in {}s. Request types are:

adbgen keeps track of the movement of the adb dot and emits adb code to move forward or backward as necessary before printing any structure member in a script. adbgen's model of the behavior of adb's dot is simple: it is assumed that the first line of the script is of the form struct_address/adb text and that subsequent lines are of the form +/adb text. The adb dot then moves in a sane fashion. adbgen does not check the script to ensure that these limitations are met. adbgen also checks the size of the structure member against the size of the adb format code and warns you if they are not equal.


If there were an include file x.h which contained:

struct x {
char	*x_cp;
char	x_c;
int	x_i;

Then an adbgen file (call it script.adb) to print it would be:

#include "x.h"

After running adbgen the output file script would contain:


To invoke the script you would type:



adb scripts for debugging the kernel


adb.1 kadb.8s

[a manual with the abbreviation DEBUG]


adb syntax is ugly; there should be a higher level interface for generating scripts.

Structure members which are bit fields cannot be handled because C will not give the address of a bit field. The address is needed to determine the offset.


Warnings about structure member sizes not equal to adb format items and complaints about badly formatted requests. The C compiler complains if you reference a structure member that does not exist. It also complains about & before array names; these complaints may be ignored.

index | Inhaltsverzeichniss | Kommentar

Created by unroff & hp-tools. © by Hans-Peter Bischof. All Rights Reserved (1997).

Last modified 21/April/97