Bugzilla – Full Text Bug Listing
| Summary: | Wrong trace output with DebugOptions.newDebugTrace(String bundleSymbolicName, Class traceEntryClass) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Clovis <clovis.seragiotto> |
| Component: | Framework | Assignee: | equinox.framework-inbox <equinox.framework-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tjwatson |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
This should be fixed in 3.5.1. *** This bug has been marked as a duplicate of bug 285292 *** |
User-Agent: Opera/9.80 (Windows NT 5.1; U; en) Presto/2.2.15 Version/10.00 Build Identifier: 20090619-0625 If you create a new DebugTrace using some traceEntryClass, the output contains only nulls for class name, method name, and line number. (I would expect the class name, method name and line number right "below" the traceEntryClass in the call hierarchy). Reproducible: Always Steps to Reproduce: Create some class Foo "to abstract tracing calls for a bundle" and, when creating the DebugTrace, use DebugOptions.newDebugTrace("myBundle", Foo.class).