Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324457 - ROV Decoding TimestampNull
Summary: ROV Decoding TimestampNull
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Rta (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Friedland CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 13:30 EDT by Chris McCormick CLA
Modified: 2015-06-02 21:01 EDT (History)
2 users (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 Chris McCormick CLA 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.