|
| Re: Debugging TTCN [message #1718879 is a reply to message #1718866] |
Thu, 31 December 2015 14:13  |
|
Hi Murli,
first of all, I understand you managed to make your test suite working; congratulations are on order; well done.
About debugging: we are working on a debugger , but that will not be ready anytime soon.
However , in our experience, with the rarest exception, the Titan logging should offer the user sufficient information to debug problematic test cases.
What can be seen from your logs is that an unexpected message is received on port U_TM which is caught by the default altstep a_UTRAN_StandardDefault
defined in UTRAN_Components.ttcn:
altstep a_UTRAN_StandardDefault() runs on UTRAN_PTC
{
:
:
[not vc_UTRAN_Global.Ctrl.DefaultCtrl.U_TM_Blocked] U_TM.receive (cr_RLC_TR_DATA_IND_Any) { // @sic R5s120098 R5s120086 sic@
all timer.stop;
f_UTRAN_SetVerdictFailOrInconc(__FILE__, __LINE__, "unexpected receive event at U_TM port");
}
the received message matches the template cr_RLC_TR_DATA_IND_Any;
However , from the log the code execution flow is not visible, and this is because some essential logging functions remained deactivated:
15:21:06.215331 TTCN Logger v2.2 options: TimeStampFormat:=Time; LogEntityName:=No; LogEventTypes:=No; SourceInfoFormat:=None; *.FileMask:=LOG_ALL; *.ConsoleMask:=LOG_ALL; LogFileSize:=0; LogFileNumber:=1; DiskFullAction:=Error
As a first step I would suggest the following:
-Activate LogEntityName, LogEventTypes, SourceInfoFormat
by setting
SourceInfoFormat:= Single //or Stack
LogEntityName:= Yes
LogEventTypes:= Yes
in the [LOGGING] section in the .cfg file; SourceInfoFormat activated will add filename/line info to the log , so it will be easier to trace the evolution of events
-also , LOG_ALL is set, but that does not cover DEBUG and MATCHING ; please add those flags too for some extra information
Detailed information about logging configuration can be found in reference guide 7.1 [LOGGING]
- I would definitely discourage you to try to trace by adding print instructions to C++ code or debugging the C++ code; I don't think that's practical; adding log statements to TTCN-3 code will bring in the information that might not be revealed by logging
In general, every kind of debugging will require and amount of understanding of the test suite, and debugging will not answer the question of what message is expected; this should be answered by the TTCN-3 code itself.
I hope this will help; if you set the logging config as above and the log file still does not answer your questions, pls. send them to me and I'll try to take a look.
Best regards
Elemer
|
|
|
Powered by
FUDForum. Page generated in 0.03423 seconds
] 
Search
Help
Register
Login
Home
