Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313966 - [LTTng] Event IRQ parsing problem
Summary: [LTTng] Event IRQ parsing problem
Status: CLOSED DUPLICATE of bug 316276
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francois Chouinard CLA
QA Contact: Francois Chouinard CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 290046
  Show dependency tree
 
Reported: 2010-05-21 14:57 EDT by Francois Chouinard CLA
Modified: 2022-01-13 14:52 EST (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 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 ***