I checked that file with traceprinter.
That's working fine, so the trace itself seams not to be corrupted
at structure level, but maybe on a semantical one.
I tried it with my 4.6.1 20090619, after 15 minutes of "trace normalization"
it fails with NullPointerException without a callstack.
So think it's an IDE issue.


-----Ursprüngliche Nachricht-----
Von:	Mario Charest [mailto:community-noreply@qnx.com]
Gesendet:	Fr 14.08.2009 19:40
An:	general-ide
Cc:	
Betreff:	Invalid .kev file.

I attached a .kev file the IDE chokes on, either version 4.7.0 or 4.6.0.  The file comes from a QNX6.4.1 machine.

I'm guessing it's an hardware problem of some sort because on an other machine, which has the same config, it works ok. 
 At anyrate you could use to file to make the system profiler more robust.

Not sure if it's related or not but pidin info report 2 cores to be of different speed then 2 other core ( it's a quad 
core machine)!!!  I'll be looking into that.  





_______________________________________________

General
http://community.qnx.com/sf/go/post36042 
 
*******************************************
Harman Becker Automotive Systems GmbH
Management Board: Dr. Klaus Blickle (Chairman), Dr. Udo Hüls, Michael Mauser
Chairman of the Supervisory Board: Ansgar Rempp | Domicile: Karlsbad | 
Local Court Mannheim: Register No. 361395

 
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat 
sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail
. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have 
received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************

Thanks Mario.

Yes, tracelogger creates semantically incorrect data when there are hardware issues related to the CPU clocks.

Traceprinter doesn't have any issues with these traces because it doesn't attempt to reorder the data and interpret it. 
It simply dumps the contents of each event as is. During the repair process IDE attempts to properly order the events in
 the trace file which can go awry when the timestamp data is incorrect.

There is a bug report open to improve the user experience in the IDE when these types of traces are encountered and to 
present the user with a more relevant error message than a NullPointerException.