# Trace Documentation Errors & Omissions

**URL:** <https://forum.sierrawireless.com/t/trace-documentation-errors-omissions/5081>\
**Category:** Documentation feedback\
**Created:** [May 25, 2011, 6:54am UTC](https://forum.sierrawireless.com/t/trace-documentation-errors-omissions/5081 "2011-05-25T06:54:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 25, 2011, 6:54am UTC](https://forum.sierrawireless.com/t/trace-documentation-errors-omissions/5081/1 "2011-05-25T06:54:55Z")

</div>

Undocumented ADL traces: [Undocumented: ADL\_TRC\_ Trace Levels used internally by ADL](https://forum.sierrawireless.com/t/undocumented-adl-trc-trace-levels-used-internally-by-adl/1371/1)

> [@ADL User Guide for Open AT® OS 6.35](#):
>
> Note: ADL trace function only supports up to 6 parameters; additional parameters are ignored.

This is not true!

The ADL trace function in the embedded Application is not limited to 6 parameters and does not ignore additional parameters.

The limitation is only in Developer Studio’s ability to display the traces - see: [DS 1.2.0 & 2.0.0 TRACE limitation](https://forum.sierrawireless.com/t/ds-1-2-0-2-0-0-trace-limitation/5049/1)

> [@ADL User Guide for Open AT® OS 6.35](#):
>
> Note: ‘%s’ character, normally used to insert strings, is not supported by the trace function.

A note should also be added about the %f bug - at least, a cross reference to where that is described

(when will this bug be fixed??)

> [@ADL User Guide for Open AT® OS 6.35](#):
>
> 3.7.4. The adl\_trcDump Function
> 
> This function dumps the required buffer content on the provided trace level. The dump will be  
> displayed in Developer Studio, according to the current context:  
> • for tasks: on the trace element name defined in the tasks declaration table (cf. Application Initialization service)

1. There is no “Application Initialization service” - it is called the Application Entry Points Interface
2. The Task Initialisation Table does not affect what flow is used - it’s always ‘ADL’

> [@ADL User Guide for Open AT® OS 6.35](#):
>
> At runtime, this will display the following string on the CUS4 level 1 on Developer Studio

“CUS4” was changed to “ADL” years ago: [Undocumented: ADL\_TRC\_ Trace Levels used internally by ADL](https://forum.sierrawireless.com/t/undocumented-adl-trc-trace-levels-used-internally-by-adl/1371/1)

> [@ADL User Guide for Open AT® OS 6.35](#):
>
> 3.1.2.2. The adl\_InitTasks\_t Structure
> 
> Name  
> Task identification string, used for debug purpose with Traces & Errors services.

I have never seen this appear anywhere in any Traces - what does this mean?