Not sure if this should be in this forum, or the OpenAT forum…
I’m using M2M Studio in conjuction with OpenAT Oasis V2.20. I’ve moved over an existing project that has a lot of TRACE() macros in it, of the form:
TRACE (( TRACE_CONFIG_READ, "config_read returns %d, Id = %d, read %u bytes", ret, id, myObjectSize ));
where TRACE_CONFIG_READ is the trace level constant, and ret, id and myObjectSize are variables to be displayed.
In previous versions of Oasis (2.02, 2.10) this TRACE statement output the values I was expecting.
In the current version of Oasis (2.20), and M2M Studio, I get the following output in the Traces View of the Target Management perspective:
config_read returns %d, Id = %d, read %u bytes
The Oasis 2.20 doco indicates that TRACE() is a macro that eventually calls adl_trcPrint() - which takes a Trace Level and a sprintf() style format string.
- Has anybody else seen this issue when using Oasis 2.20 & M2M Studio?
- Is it an issue with M2M Studio or Oasis 2.20?
- Is there a workaround (other than manually constructing the string using wm_sprintf())