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

Bug 313966

Summary: [LTTng] Event IRQ parsing problem
Product: z_Archived Reporter: Francois Chouinard <fchouinard>
Component: LinuxToolsAssignee: Francois Chouinard <fchouinard>
Status: CLOSED DUPLICATE QA Contact: Francois Chouinard <fchouinard>
Severity: normal    
Priority: P3 CC: patrick.tasse
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 290046    

Description Francois Chouinard CLA 2010-05-21 14:57:49 EDT 
On occasion, there is an invalid IRQ being parsed which causes the StateProvider to experience an NPE. The code was modified so it recovers from the NPE and prints a message at the console.

E.g.: Invalid irq (15397), ts = 14453.291124725

Looking at the EventsView, it turns out that the actual IRQ (and only the IRQ field) was corrupted i.e. it is OK in the EventsView and it is bad when passed to the StateProvider.

To reproduce:

- Remove the trace in StateUpdateHandlers.getIrqEntryHandler()
- In the debugger, add a breakpoint for NPE

Drilling into the events structure will show that this field is corrupted wrt the actual event content.
Comment 1 Francois Chouinard CLA 2010-06-21 15:41:46 EDT 
This was apparently caused by concurrent access to the underlying parsing library by using 2 distinct file descriptors: the library doesn't seem to be as thread-safe as advertised.

The current solution to access the lib involves only 1 prioritized requests queue and a single event processor that prevents concurrent accesses.

Problem has not occurred since Bug316276 was implemented.
Comment 2 Francois Chouinard CLA 2010-07-08 10:17:35 EDT 
Released in a past delivery.
Comment 3 Patrick Tasse CLA 2013-05-24 15:05:44 EDT 

*** This bug has been marked as a duplicate of bug 316276 ***