ttcn3_logformat different otput format during unmatched text string
Summary
In "unmatched: First message in the queue does not match the template" log lines, ttcn3_logformat prints output formatted differently:
- As "}\n,{" in the "got" section
- As "}, {" in the "exp" section.
Steps and/or TTCN-3 code to reproduce
Take a long log line printing a "unmatched: First message in the queue does not match the template" case (see log.merged attached). This is basically of the sort "[...] with [...] format. I run ttcn3_logformat on it. I split manually the text into "got" file, and the text into the "exp" case. I use "meld" difftool to figure out the difference between the received (got) and expected (exp) message. Lot of lines differ, because the text is formatted as "}\n,{", while the text is formatted as "}, {".
Not sure if the difference is due to "got" vs "exp" sections, or because the "exp" has the AVPs inside a "superset".
What is the current bug behavior?
Different whitespace formatting is printed by ttcn3_logformat when re-encoding the same line.
What is the expected correct behavior?
The same format should be applied for whitespace everywhere to make diffing easy.
Relevant logs and/or screenshots
See attached files: exp.txt
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Titan version
$ ttcn3_compiler -v
TTCN-3 and ASN.1 Compiler for the TTCN-3 Test Executor
Version: 9.0.0
Build date: Sep 22 2023 23:38:05
Compiled with: GCC 13.2.1
Using OpenSSL 3.2.1 30 Jan 2024
Commit id: 67573c4
Copyright (c) 2000-2023 Ericsson Telecom AB
Platform details (OS type and version)
Linux.
/cc @aknappqwt @mmagyari