Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project
  
Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005827ETSI TTCN-3 Quality CheckerT3Q toolpublic26-11-2010 12:3822-02-2012 09:48
ReporterMiguel Angel Reina Ortega 
Assigned ToPhilip Makedonski 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in VersionRelease 1.0.0 
Summary0005827: Log statements containing variables generates format warnings
DescriptionOne log statement containing variables between pieces of text generates format warnings. Example:

log("*** f_function: INFO: Unknown component " & p_variable & " ***");

Lib_Functions.ttcn: 1041: WARNING: Log Statements: Invalid log format ("")! (5.1. checkLogFormat)
Lib_Functions.ttcn: 1041: WARNING: Log Statements: Invalid log format ("TemplateInstance")! (5.1. checkLogFormat)
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0010000)
Philip Makedonski (developer)
08-05-2011 21:15

 The fix for this, along with a related fix for processing subsequent log statements as one, is included in the updated builds for v1.0.2.
(0010548)
Miguel Angel Reina Ortega (reporter)
16-02-2012 15:09

 v1.0.2 does not fix yet this issue.

Note that p_variable can be anything, i.e. a variable (v_myVariable, a constant (c_myConstant), a parameter (p_myParameter), a result from a called function ( int2str(v_myVariable), etc...
(0010550)
Philip Makedonski (developer)
21-02-2012 12:28

 No sure which build of v1.0.2 you are using, however there are releases for v1.0.3 available now, which integrate the aforementioned fixes. In general, all non-charstring elements (variable references, constant references, parameter references, function calls, etc.) are ignored when checking the log format. Note however, that currently charstring elements used as actual parameters in function calls will be taken into consideration as well, e.g.:

//correct - function calls are ignored
        log("*** f_1: " & getMyStatus() & "INFO: OK - random value = " & bit2str(v_random) & " ***");
        
        //incorrect - charstring function call parameters are taken into consideration resulting in an incorrect log statement format
        log("*** f_1: " & getMyStatus("1") & "INFO: OK - random value = " & bit2str(v_random) & " ***");

Variable values, constant values, parameter values, function return values etc. are not checked as these are only available at runtime in general.

Another thing to note is that superfluous warnings may be generated from the legacy checkLogItemFormat if it is enabled. This check is now deprecated and you should disable it and only use checkLogStatementFormat instead.

Please check the new releases or latest builds for v1.0.2, if, for some reason, you would rather not update to v1.0.3 just now and report back if there is still an issue with this.
(0010554)
Miguel Angel Reina Ortega (reporter)
22-02-2012 09:37

 Right, version 1.0.3 solves the issue, therefore it can be marked as resolved.

- Issue History
Date Modified Username Field Change
26-11-2010 12:38 Miguel Angel Reina Ortega New Issue
26-11-2010 12:38 Miguel Angel Reina Ortega Status new => assigned
26-11-2010 12:38 Miguel Angel Reina Ortega Assigned To => Philip Makedonski
08-05-2011 21:15 Philip Makedonski Status assigned => resolved
08-05-2011 21:15 Philip Makedonski Fixed in Version => Release 1.0.0
08-05-2011 21:15 Philip Makedonski Resolution open => fixed
08-05-2011 21:15 Philip Makedonski Note Added: 0010000
16-02-2012 15:09 Miguel Angel Reina Ortega Status resolved => feedback
16-02-2012 15:09 Miguel Angel Reina Ortega Resolution fixed => reopened
16-02-2012 15:09 Miguel Angel Reina Ortega Note Added: 0010548
21-02-2012 12:28 Philip Makedonski Note Added: 0010550
22-02-2012 09:37 Miguel Angel Reina Ortega Note Added: 0010554
22-02-2012 09:48 Philip Makedonski Status feedback => resolved
22-02-2012 09:48 Philip Makedonski Resolution reopened => fixed

MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker