Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317131 - Parameter of type Log_Event causes incomplete ENTRY trace of ILogger write functions
Summary: Parameter of type Log_Event causes incomplete ENTRY trace of ILogger write fu...
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Runtime (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Sasha Slijepcevic CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-16 19:53 EDT by Sasha Slijepcevic CLA
Modified: 2012-06-04 14:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sasha Slijepcevic CLA 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.