Knowledge Base

BSPs and drivers

Community resources

Product documentation

Questions?

traceprinter returns "TRACEPARSER: function call traceparser() failed, internal error code(15)"

________________________________________________________________________

Applicable Environment

________________________________________________________________________

Topic: Traceprinter: traceparser() failed, internal error code (15)
SDP: 7.1.0
Target: All supported targets

________________________________________________________________________

Issue

________________________________________________________________________

Traceprinter is exiting prematurely with the following error:

"TRACEPARSER: function call traceparser() failed, internal error code(15)"

The end of the output file reports:

"Can't find header end, results may be invalid"

How can I fix this?

________________________________________________________________________

Solution

________________________________________________________________________

Confirm whether the KEV file name created by tracelogger does not contain multiple "T" characters.

If KEV file name contains multiple "T" characters, and you still wish to capture the log, please try the following
- create a backup copy of the KEV file
- open the KEV file
- look for TRACE_FILE_NAME:: and TRACE_TRACELOGGER_ARGS::
- replace the "T" in the filename with 't"
- rerun traceprinter

Version of traceprinter effected:
# use -i /tmp/traceprinter
QNX_BUILDID=(GNU)adaec34589d606b212f3af6fac6fc0ce
NAME=traceprinter
DESCRIPTION=Utility to display tracelogger output
DATE=2020/06/13-20:49:16-EDT
STATE=stable
HOST=sdp710-node1
USER=builder
VERSION=7.1.0
TAGID=710-SDP-472

PACKAGE=com.qnx.qnx710.target.microkernel.tools/0.0.2.00472T202006132107S

________________________________________________________________________

NOTE: This entry has been validated against the SDP version listed above. Use caution when considering this advice for any other SDP version. For supported releases, please reach out to QNX Technical Support if you have any questions/concerns.

________________________________________________________________________

Related Attachments

None Found

Please contact us with your questions or concerns.