7.  Anomalies

      Below is a list of some strange things that users should be aware of.

1.

Function calls and arguments are put on the stack by the C save routine. Putting breakpoints at the entry point to routines means that the function appears not to have been called when the breakpoint occurs.

2.

When printing addresses, ADB uses either text or data symbols from the a.out file. This sometimes causes unexpected symbol names to be printed with data (e.g. savr5+022). This does not happen if ? is used for text (instructions) and / for data.

3.

ADB cannot handle C register variables in the most recently activated function.