Using PEEDI
Section OS
This section contains parameters which help PEEDI scan the target OS task list.
ITEM
Synopsis:
ITEM = <type_access>, <name>, <offset> [, offset[,
offset]]
Description:
type
- type of the field:
•
int - item is an integer number
•
reg - item is a CPU register
•
str - item is a string
•
access
- what memory access to be used to read:
•
4x8 - 32-bit value using 8-bit access
•
2x16 - 32-bit value using 16-bit access
•
32 - 32-bit value using 32-bit access
•
8x8 - 64-bit value using 8-bit access
•
4x16 - 64-bit value using 16-bit access
•
2x32 - 64-bit value using 32-bit access
•
64 - 64-bit value using 64-bit access
type_access
argument might has a
_abs
suffix, which means that the address calculated
of the
offset
parameters is an absolute memory location, not an offset from the base of
the task.
name
- name of the item, might be a CPU register name or some of there:
•
BASE - it tells PEEDI the item is the base address of the task OS list
•
NEXT - it is a pointer to the next task in the list
•
PID - it is the process ID of the task
•
NAME - it is the human readable name of the task
offset
- offset of the item in the task list, multiple offsets may be used for a pointer-to-
pointer like behavior
As
offset
a valid application symbol might be used, this way, upon GDB connection,
PEEDI will ask GDB for the address of the given symbol and use it.
Example:
PEEDI User’s Manual
84
