Received: from qnxmail.qnx.com (192.168.1.11 [192.168.1.11]) by nimbus.ott.qnx.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id YGGV5YT1; Thu, 13 Dec 2007 08:35:30 -0500
Received: from nimbus.ott.qnx.com (exch.ott.qnx.com [10.42.3.10])
	by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id IAA04253
	for <cburgess@qnx.com>; Thu, 13 Dec 2007 08:35:19 -0500
Received: from community.qnx.com (192.168.1.220 [192.168.1.220]) by nimbus.ott.qnx.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id YGGV5YS0; Thu, 13 Dec 2007 08:35:26 -0500
Received: from localhost.localdomain ([127.0.0.1])
          by community.qnx.com (JAMES SMTP Server 2.2.0) with SMTP ID 936
          for <cburgess@qnx.com>;
          Thu, 13 Dec 2007 08:34:42 -0500 (EST)
Message-ID: <9574375.1197552882177.JavaMail.sf-admin@community.qnx.com>
From: Thomas Fletcher <thomasf@qnx.com>
Reply-To: post3732@community.qnx.com
To: general-ide <post3732@community.qnx.com>
Subject: RE: "CPU Usage" is reporting wrong threads
Date: Thu, 13 Dec 2007 08:34:42 -0500
MIME-Version: 1.0
In-Reply-To: 30998691.1197533625766.JavaMail.sf-admin@community.qnx.com
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C83D94.D40072F4"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C83D94.D40072F4
Content-Type: text/plain;
	charset="iso-8859-1"

 

> -----Original Message-----
> From: Hans-Peter Reicher [mailto:hpreichert@harmanbecker.com] 
> Sent: December 13, 2007 3:14 AM
> To: general-ide
> Subject: "CPU Usage" is reporting wrong threads
> 
> The build 200712061800 has a problem in the "CPU Usage" reporting.
> obviousley the reported threads are shifted by one.
> So the CPU usage reported for Thread 3 is indeed the usage of 
> Thread 2.
> You see this in all CPU usage realted views as "Event Owner 
> Stats" or the "Client/Server CPU stats"

What version of the OS is the logfile you are looking at being
generated from?  There was a bug in the 6.3.2 release where the 
thread name information was being emitted with the internal kernel
thread id, which meant that it was one off of the normal id. 

This should only affect you if you are using thread names however.

Can you double check the Properties view for the log file you 
are looking at and provide the information on the version of 
the OS you are tracing.

Thanks,
 Thomas

_______________________________________________
General
http://community.qnx.com/sf/go/post3732

------_=_NextPart_001_01C83D94.D40072F4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: &quot;CPU Usage&quot; is reporting wrong threads</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Hans-Peter Reicher [<A =
HREF=3D"mailto:hpreichert@harmanbecker.com">mailto:hpreichert@harmanbeck=
er.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: December 13, 2007 3:14 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: general-ide</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: &quot;CPU Usage&quot; is reporting =
wrong threads</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The build 200712061800 has a problem in the =
&quot;CPU Usage&quot; reporting.</FONT>
<BR><FONT SIZE=3D2>&gt; obviousley the reported threads are shifted by =
one.</FONT>
<BR><FONT SIZE=3D2>&gt; So the CPU usage reported for Thread 3 is =
indeed the usage of </FONT>
<BR><FONT SIZE=3D2>&gt; Thread 2.</FONT>
<BR><FONT SIZE=3D2>&gt; You see this in all CPU usage realted views as =
&quot;Event Owner </FONT>
<BR><FONT SIZE=3D2>&gt; Stats&quot; or the &quot;Client/Server CPU =
stats&quot;</FONT>
</P>

<P><FONT SIZE=3D2>What version of the OS is the logfile you are looking =
at being</FONT>
<BR><FONT SIZE=3D2>generated from?&nbsp; There was a bug in the 6.3.2 =
release where the </FONT>
<BR><FONT SIZE=3D2>thread name information was being emitted with the =
internal kernel</FONT>
<BR><FONT SIZE=3D2>thread id, which meant that it was one off of the =
normal id. </FONT>
</P>

<P><FONT SIZE=3D2>This should only affect you if you are using thread =
names however.</FONT>
</P>

<P><FONT SIZE=3D2>Can you double check the Properties view for the log =
file you </FONT>
<BR><FONT SIZE=3D2>are looking at and provide the information on the =
version of </FONT>
<BR><FONT SIZE=3D2>the OS you are tracing.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>&nbsp;Thomas</FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>General</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://community.qnx.com/sf/go/post3732" =
TARGET=3D"_blank">http://community.qnx.com/sf/go/post3732</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C83D94.D40072F4--
