Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317131

Summary:	Parameter of type Log_Event causes incomplete ENTRY trace of ILogger write functions
Product:	[Technology] RTSC	Reporter:	Sasha Slijepcevic <sascha>
Component:	Runtime	Assignee:	Sasha Slijepcevic <sascha>
Status:	ASSIGNED ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	dfriedland
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Sasha Slijepcevic

2010-06-16 19:53:17 EDT

The first parameter of ILogger write functions is an encoded type Log_Event. If diags_ENTRY is enabled for an ILogger implementation, log entries for such events do not contain all parameters of a function call.
The code in Config.java that generates the code that logs ENTRY events cannot figure out the output conversion for encoded types, so it generates the code that only prints function call parameters up to the encoded type.

The relevant functions are Config.genFxnBody, which calls Glob.fmtSpec.

This is an edge condition because logging of loggers is discouraged, but we have an example in examples.runtime.logger in the xdc tree, where an additional logger Filter is on top of LoggerSys. Filter's ENTRY events are logged, but the output is incomplete.

The change that caused this problem happened between xdc-v25 and xdc-v26, when we switched from Types_Event (Bits32) to Log_Event.