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

Bug 324457

Summary:	ROV Decoding TimestampNull
Product:	[Technology] RTSC	Reporter:	Chris McCormick <c-mccormick>
Component:	Rta	Assignee:	David Friedland <dfriedland>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	d-russo, dfriedland
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Chris McCormick

2010-09-03 13:30:27 EDT

If an application has TimestampNull plugged, the Timestamp is reported as ~0 for both lo and hi. This value is too large to display in a 64-bit signed Java long, so it ends up coming out as a funky number: 9223372036854776000 (0x0800 0000 0000 00C0). The Decoder already contains some logic for dealing with too-large timestamps, but apparently it doesn't deal nicely with this scenario. Ideally, RTA and the LoggerBuf ROV view should display something intelligent for the timestamp, like -1 or 0 or something.